5,838
edits
Updating MX to new version: Difference between revisions
m
→Updating to a new major version
| Line 109: | Line 109: | ||
*Schema changes for database tables | *Schema changes for database tables | ||
=== What you need to read === | |||
*Basically, check the corresponding release announcements for every version since the one you have been using before planning your upgrade. | |||
**Make a note of any one-off actions required at particular in-between versions, remember these actions are only in forum release announcements. | |||
**Although one-off actions will not be described in the Wiki (whether on the [[Software]] page or the [[Cumulus_MX_formal_release_versions]] page), the Wiki can give you an idea of what functionality has been improved to help you decide whether to update. | |||
*It is still worth reading all the points made above for updating from immediately preceding build. | |||
==Updating from a very old version== | |||
Many people believe if it works, it don't need fixing. So they install whatever MX version is available when they start using MX and ignore all the bug fixing and new functionality being added, and stick with their existing installation. | |||
Suddenly they realise that perhaps their version does lack functionality that would be useful to them. Maybe their version does not have an editor for correcting rogue extreme records and they realise correcting log files is something that is hard for them to do. | |||
This section is therefore included to give advice on why you should not jump from an old version to the latest directly, but how it can be safely done in stages. | |||
= Recommended Actions when Updating = | = Recommended Actions when Updating = | ||