Updating MX to new version: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
m (→‎From 3.9.y releases: renamed sub-section)
(2 intermediate revisions by the same user not shown)
Line 289: Line 289:


The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].
The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].


====Currently using one of the 3.9.y releases ====
====Currently using one of the 3.9.y releases ====
Line 305: Line 310:
Note:  The folder <code>CumulusMX/webfiles-legacy</code> mentioned in the new default web site information page, with some alternative web pages that have no ongoing support, is only available from a 3.10.0 or 3.10.1 download (find from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).
Note:  The folder <code>CumulusMX/webfiles-legacy</code> mentioned in the new default web site information page, with some alternative web pages that have no ongoing support, is only available from a 3.10.0 or 3.10.1 download (find from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).


====if using either 3.8.x or 3.9.y release====


See next sub-section, that describes similar process, '''upgrade directly to 3.9.6, or any later build, within 3.9.x''', without any major change.






====if using any 3.7.y release, upgrade to 3.9.6 before going further ====
====if using 3.7.0 release, any 3.8.x  release, or 3.9.y release====
 
See sub-section directly above, that describes similar process,
* EITHER '''upgrade directly to 3.9.6, or any later build, within 3.9.x, without any major change,'''
* or to 3.12.0 with major change
*  (find either release from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).
 
If you are using  a release earlier that 3.7.0, you can note 3.7.0 was only build in 3.7.y series, but because 3.7.0 introduced a lot of changes these staged upgrades recommend that 3.7.0 is implemented, and run for a while, before continuing to upgrade.
 
Be aware that 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service, but there is no reason to install it as the ability to run either interactively, or as a service, continues to be available in all subsequent releases.


It is optional to install release 3.9.6 build 3101, because that is a safe release to use while there were bugs in the builds in all 3.8.z versions, and in other 3.9.x releases, however please action the one-off changes noted as IMPORTANT here:


'''IMPORTANT''' one-off actions needed:
'''IMPORTANT''' one-off actions needed:
Line 318: Line 331:
* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.
* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.


 
Be aware that 3.10.0 was withdrawn, but it was a major release that totally changed the files in [[Web folder]] and [[Webfiles folder]] within the release download. However, you can skip directly from 3.9.6 (if you have implemented that) to 3.12.0 as soon as you are happy to change your web server contents (if you are using web pages that MX provides), see sub-section above for further advice re web pages.  You should continue in stages because it is mandatory to install 3.12.0 as only that release can rewrite your [[Cumulus.ini]] file ready for subsequent release, so ensure that 3.12.0 is working before installing current release as instructed in sub-sections for those using subsequent releases.
 
If you are using 3.7.0 (there were no other builds in 3.7.y series), then you should upgrade directly to version 3.9.6 - build 3101.
 
Only 3.7.0 was ever released, it introduced a lot of changes, so that is why staged upgrades recommend that this version is implemented, and run for a while, before continuing to upgrade.
 
Version 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service. However, there were bugs in the builds in all 3.8.z versions, and in some 3.9.x versions, so that is why you need to skip through intermediate builds below 3101.
 
 
When you are happy with running version 3.9.6 build 3101, you can continue to upgrade.  You should continue in stages by going to 3.10.x, and ensure that is working before installing a later release as instructed for those using 3.10.x releases.
 


====If using a 3.5.x release ====
====If using a 3.5.x release ====
Line 347: Line 350:
*'''If you use commas to separate integer and decimal parts of real numbers''', then various releases from 3.6.0 to 3.7.0 add "rc=y" to various web tags, that option will replace the decimal commas you use by decimal points that are required for some script languages (like the JavaScript used by HighCharts), and that makes it easier if you want to customise your web site.
*'''If you use commas to separate integer and decimal parts of real numbers''', then various releases from 3.6.0 to 3.7.0 add "rc=y" to various web tags, that option will replace the decimal commas you use by decimal points that are required for some script languages (like the JavaScript used by HighCharts), and that makes it easier if you want to customise your web site.


When you are happy with running 3.7.0, then you should continue to upgrade, but in steps (3.7.0 to 3.9.6, then 3.9.6 to 3.10.y, then exactly 3.12.0, then latest) as described in earlier sub-sections for later releases.
When you are happy with running 3.7.0, then you should continue to upgrade, but in steps (optionally try 3.9.6 because that will test some new features, then mandatory upgrade to exactly 3.12.0 which will rewrite your Cumulus.ini file, then you can continue your upgrade to latest) as described in earlier sub-sections for later releases.




Line 354: Line 357:
====If using either 3.1.x, 3.2.y, 3.3.z, or 3.4.w releases====
====If using either 3.1.x, 3.2.y, 3.3.z, or 3.4.w releases====


First, upgrade to 3.5.1 by downloading it at [[https://github.com/cumulusmx/CumulusMX/releases/tag/b3072 Mark's Github respository]]. The actual installation is done using the instructions early in this Wiki page for simple next build upgrades. You can safely skip reading the intermediate release announcements, as there are no special one-off actions.
First, upgrade to 3.5.1 by downloading it at [[https://github.com/cumulusmx/CumulusMX/releases/tag/b3072 Mark's Github respository]]. The actual installation is done using the instructions early in this Wiki page for simple next build upgrades. You can safely skip reading the intermediate release announcements, as there are no special one-off actions.  There are one-off actions at 3.5.1, see release announcement.  It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.




When you are happy running 3.5.1, then you should continue to upgrade, initially follow instructions given forlater releases
When you are happy running 3.5.1, then you should continue to upgrade, initially follow instructions given for later releases




Line 366: Line 369:
====If using 3.0.0 (the MX original beta)====
====If using 3.0.0 (the MX original beta)====


Upgrade from the beta directly to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072.
 
Upgrade from the beta directly to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072.  There are one-off actions at 3.5.1, see release announcement. This skips you past the problems in 3.5.0. It gives you benefits introduced in 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases.


This gives you essential new functionality in the admin interface like editors for the log files and extreme records. But it also fixes multiple bugs in the beta you were using and adds some useful validation missing in the beta.
This gives you essential new functionality in the admin interface like editors for the log files and extreme records. But it also fixes multiple bugs in the beta you were using and adds some useful validation missing in the beta.
Line 372: Line 376:
It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.
It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.


It skips you past the problems in 3.5.0. It gives you benefits introduced in 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases.


Now follow instructions in other sub-sections, to upgrade in stages until you reach latest release and get support from developer.
Now follow instructions in other sub-sections, to upgrade in stages to where there are significant actions to do, until you reach latest release and get support from developer.


= Knowing when a new release is available =
= Knowing when a new release is available =
5,838

edits

Navigation menu