Changes between Version 54 and Version 55 of SysAdmin/ReleaseProcess


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

--

Legend:

Unmodified
Added
Removed
Modified
  • SysAdmin/ReleaseProcess

    v54 v55  
    3737* https://git-scm.com/book/en/v2/Git-Basics-Tagging
    3838
    39 === Branch Tags ===
    40 If 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
     39=== Deployment Branches ===
     40If a Branch of the code is made to manage releases for a deployment, then there are 2 options:
     41* If any significant development is done then it should be based initially off trunk
     42* If no development is planned (just backporting any critical bugfixes) then it can be based off stable right away
     43
     44Once a Development branch moves into Production then it should move to being based off Stable (or could even start using vanilla stable releases).
     45
     46Branches based off Stable should have it's version appended to that of the Stable branch, so:
    4147{{{
    4248[BranchName]-[Major].[Minor].[Sub]-[BranchRelease].[Sub]
    4349}}}
    4450
     51Branches based off Trunk should have it's version appended to the Major Version of the Trunk branch, so:
     52{{{
     53[BranchName]-[Major]-[BranchRelease].[Sub]
     54}}}
     55
     56If a production site has another Development phase then a new Development branch should be created for that, again starting from Trunk. This can be deployed to the Dev server.
     57When ready to move that branch to production then it should be rebased off stable & then Test updated from there.
    4558== Upgrade Scripts ==
    4659For every update that requires it, an Upgrade script will be added to: