Changes between Version 52 and Version 53 of SysAdmin/ReleaseProcess


Ignore:
Timestamp:
03/12/16 11:10:35 (6 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SysAdmin/ReleaseProcess

    v52 v53  
    1919The VERSION string will include the Tag + the number of commits since the last tag + the hash of the commit
    2020
    21 The Major release number will only change if we:
     21The Major version number will only change if we:
    2222* create a new parallel branch which would become the new trunk
    2323* probably this would be because we change the API in backward-incompatible ways
     
    2727* These will often require an update script
    2828
    29 The Sub release number indicates an update to the release.
     29The Sub release number indicates a maintenance update to the release.
    3030Sub-releases can introduce new features, but they would normally not:
    3131- replace feature sets
    3232- remove feature sets
    3333- fundamentally change the logic/semantics of a feature set
    34 Sub-releases may still require an upgrade script, but usually won't. They normally wouldn't need user communications.
     34Sub-releases may still require an upgrade script, but usually won't. They normally wouldn't need such stringent user communications or documentation updates.
    3535
    3636Git docs on Tags: