Cumulus MX formal release versions: Difference between revisions

Cumulus MX formal release versions (view source)

Revision as of 08:42, 25 July 2020

1,386 bytes added , 08:42, 25 July 2020

m

→‎Information included in this article

Sfws

5,838

edits

@@ Line 13: / Line 13: @@
 == Information included in this article ==
+Please note that the support files (e.g. those in folder interface) are not part of the commit when creating CumulusMX.exe.  This can lead to the zip provided in the release download not matching the release description in the formal announcement. In extreme cases, as some entries in tables below show, it has been flagged where the wrong files are included.
 The tables below include
 * version number,
-* date of release,
+* date of release (date when the principal changes in the build were first available in a public release),
+**please note that changes to some support files included in a release zip may be made after the build release date without being announced as a new build, and sometimes updated support files have accidentally appeared in zip for an earlier release than that of formal release.
 * build number,
-* summarises of both fixes and new features,
+* summary of any fixes or improvements to existing functionality
-* plus indicates of which files have been updated or added. Please note that as "Updates.txt" is updated in every release it does not normally appear in any list below of files that have been updated in an individual release. If you are only copying updated files then always copy in this file, as well as any listed.
+*summary of any new functionality made available in build
+*Basic indication of those files that have been updated, removed, or added.
+**Please note that as "Updates.txt" is updated in every release it does not normally appear in any list below of files that have been updated in an individual release. If you are only copying updated files then always copy in this file, as well as any listed.
+** In a few releases the files included in the zip have had some inconsistencies with what is reported as the changed files. This is generally because either a particular correction was made in advance of other preparation for a new release and forgotten about, or because a minor correction was made after the formal release.
+**For the rare case where the files included are not matched with the commit to form the executable, this may mean although you have a working release for most aspects of MX, some functionality within MX does not work at that release.
 == Instructions ==