Changes between Version 49 and Version 50 of SysAdmin/ReleaseProcess

03/11/16 17:07:03 (8 years ago)
Fran Boon

Proposal for new Release Process


  • SysAdmin/ReleaseProcess

    v49 v50  
     4We plan to make release versions of Eden.
     6This will entail:
     7* Creating a QA branch
     8 - features have final integration testing done here before being pushed to the Stable branch
     9* Creating a Stable branch
     10 - deployments should be done from this branch
     11* Adding Tags to Releases
     12* Building upgrade scripts
     14== Tagging ==
     15Tags will be added based on the following schema:
     19The VERSION string will include the Tag + the number of commits since the last tag + the hash of the commit
     21The Major release number will only change if we:
     22* change the API in backward-incompatible ways
     23* release a new trunk
     25The Minor release number indicates the normal release.
     26[[BR]]These will often require an update script
     28The Sub release number indicates an update to the release.
     29Sub-releases can introduce new features, but they would normally not:
     30- replace feature sets
     31- remove feature sets
     32- fundamentally change the logic/semantics of a feature set
     33Sub-releases may still require an upgrade script
     35Git docs on Tags:
     38=== Branch Tags ===
     39If a Branch of the code is made on GitHub to manage releasesfor a deployment, then it's version will be appended to that of the Stable branch, so
     44== Upgrade Scripts ==
     45For every update that requires it, an Upgrade script will be added to:
     49The 'pull' script will be modified to call this script automatically
     51=== Template Upgrade Scripts ===
     52If there are template-specific changes for an update then these will be found in:
     56This will be checked for automatically by the 'pull' script
     58=== Branch Upgrade Scripts ===
     59Typically a Branch will be using a custom Template (even if this is a thin layer on top of other templates).
     61Branch upgrade scripts will therefore be in:
     67This will be checked for automatically by the 'pull' script.
     69If there is no branch-specific upgrade script yet there is one for the underlying stable upgrade then the pull script should detect this & allow the user to run this instead of nothing or bail & revert.
     71== Old Info ==
    472When making a Stable Branch from which to build releases, we need to do these tasks:
    76144 * Reboot VPS (free up resources for improved performance)
    78 === Ideas ===
     146=== See Also ===
    79147 * [ Systers release process]
    80148 * [ OpenBSD release process]