home *** CD-ROM | disk | FTP | other *** search
- UPGRADE Policy
- ==============
-
- The UPGRADE request is used to upgrade your copy of MailList in one of the
- following instances:
-
- o When it has been shown that the current release of the application is too
- unstable or contains a nasty bug and needs to be fixed as soon as
- possible.
-
- o When one of the files in the release needs to be updated but is not worth
- a completely new release.
-
- The UPGRADE request will be processed by your Robot. It will make a backup
- copy from the file to be upgraded first. This will allow you to change back
- to the old situation if you desire to do so.
-
- Once a file has been replaced by an upgraded version. At least 7 days will
- pass before I will issue another UPGRADE request on the same file. Provided
- ofcourse that it is necessary to upgrade the same file so quickly. This will
- allow you to find out whether the new version is stable or has any new bugs
- and report them to me.
-
- Version-numbering
- =================
-
- o The version-number is increased by 0.01 for every new release of the
- software.
-
- o The version-number is increased by 1.00 when the previous release of the
- software is not compatible with the new release. In such a case the
- decimals of the version number are reset to .00
-
- o In case an UPGRADE of the !RunImage is issued, the version-number of the
- application will be hardcoded into the !RunImage and a letter will be
- added to distinguish it from the original release. Eg. v0.10 was upgraded
- to fix some problems with NewsBase 0.53. The new versionumber became
- 0.10a.
-
-
-
- *** Comments/suggestions are welcome ***
-