Upgrading xTuple Manufacturing 3.5.0
Few people may realize that, behind the scenes, xTuple ERP 3.4.0 represented a major overhaul to how the software is put together. For that release we didn't just use extension packages to add on to the xTuple core, we converted core functionality into packages. "Huh?" you say...
Beginning with 3.4.0, we turned xTuple ERP Manufacturing Edition into a separate extension package, xtmfg. This new approach will allow for more real-time bug fixes and provide examples for customers who want to know more about creating and modifying packages.
However, the process of upgrading has become a bit more involved, too. This is because, in the 3.5.0 release cycle, you'll need to upgrade both your core database as well as the xtmfg package. The good news is, you use the same tool for both jobs: the xTuple Updater.
Here's an example of the process for upgrading your xTuple Manufacturing database for the 3.5.0 final release in 3 easy steps:
- Backup your database
- Update using the Standard Edition upgrade script (e.g., std340to350.gz)
- Update your xtmfg package (e.g., xtmfg-340to350.gz)
A couple of things to consider:
- Not every in-between release will have an xtmfg package update. The 3.5.0 Alpha, 3.5.0 Beta2, 3.5.0 Beta 3, 3.5.0 RC, and 3.5.0 final have changes to the xtmfg package. You will not find/need one for the Beta release.
- In the final release, you will have one standard upgrade script and one xtmfg upgrade script to go from 340 to 350. So it might look messier during the alpha/beta/RC testing cycles - but migrating from one official release to the next will only be the two files, as described above.
- If you are upgrading through more than one release at a time, it is always a good idea to log out of the updater and then log back in. This is not necessary within the same release, i.e., you do not have to log out to apply the xtmfg package after updating the Standard upgrade script.
- For more information on upgrading check out the Updater Guide.
Still confused about something? add a comment :)
- mmcbride's blog
- Login or register to post comments
Step 4 (optional) would be to update your
It seems that with the release of 3.5 (or 3.5.1 for Standard Edition porting to an Updater Package per the recent roadmap), changes to the core would follow a much slower release cycle, n'est-ce pas?
Thank you, this helps!
With the architecture of 3.4 being so different, should I upgrade my 3.1 installation to 3.4 before upgrading to 3.5?
You would have to go through 3.4 on the way to 3.5 anyway ...
310to320.gz
320to321.gz
321to322.gz
322to330.gz
330to331.gz
331to340.gz
... then the steps Monique outlined above.
You might want to consider our XTN service, which applies the updates for you automatically - first on a pilot database for you to test, then on your production system. Please contact xTuple sales if you're interested.
We are using database 3.5.0beta3 (Manufacturing), how can we upgrade to 3.5.0RC or 3.5.0?
As I cannot found file of 350beta3to350rc.gz or 350beta3to350.gz, please help. Thanks.
Hi, valentin:
Due to an error on our end, those files were missing temporarily. However, they have been put back. Please check again and you should find them. Sorry for any inconvenience....
Regards,
Pierce
