5,838
edits
Cumulus MX formal release versions: Difference between revisions
m
→Instructions
m (→Revision Date) |
m (→Instructions) |
||
|
As that topic name suggests you should read it before you upgrade to a new release. If you are intending to upgrade to any new release, please read all of the release notes since the build you are currently running.
=== If you only want to update those files that have changed since the release you are currently using ===
'''It is always worth checking the date modified for every file in any release''', to ensure you include all updated files, not just that the developer remembered to include in the list of changed files. At the time I typed this, there were '''261 files spread through 57 folders in each release zip'''. Since the developer updates different files at different times, in-between releases, even the tracking facilities of Git Hub can make it hard to keep track of all files changed. Don't forget the developer is updating Cumulus MX in his spare time, he has a life outside MX.▼
Best practice is to copy all files included in the release zip irrespective of whether they have changed or not, but this could mean a lot of extra transfers you want to avoid.
The problem is that changes may be made to the source at various times, and the developer my not recall all changes made when a new release is made, especially if it is rushed out to fix a bug.
▲
'''It is always worth checking the date modified for every file in any release''', to ensure you include all updated files, not just those the developer remembered to include in the list of changed files that appears in each announcement.
At the time I typed this, there were '''261 files spread through 57 folders in each release zip'''. It is possible as you read this, that file count has been increased due to extra functionality!
{{TOCright}}
| |||