Changes between Version 49 and Version 50 of SysAdmin/ReleaseProcess

Timestamp:

03/11/16 17:07:03 (10 years ago)

Author:

Fran Boon

Comment:

Proposal for new Release Process

SysAdmin/ReleaseProcess

@@ -2 +2 @@
 [[TOC]]
 
+We plan to make release versions of Eden.
+
+This will entail:
+* Creating a QA branch
+ - features have final integration testing done here before being pushed to the Stable branch
+* Creating a Stable branch
+ - deployments should be done from this branch
+* Adding Tags to Releases
+* Building upgrade scripts
+
+== Tagging ==
+Tags will be added based on the following schema:
+{{{
+[BranchName]-[Major].[Minor].[Sub]
+}}}
+The VERSION string will include the Tag + the number of commits since the last tag + the hash of the commit
+
+The Major release number will only change if we:
+* change the API in backward-incompatible ways
+* release a new trunk
+
+The Minor release number indicates the normal release.
+[[BR]]These will often require an update script
+
+The Sub release number indicates an update to the release.
+Sub-releases can introduce new features, but they would normally not:
+- replace feature sets
+- remove feature sets
+- fundamentally change the logic/semantics of a feature set
+Sub-releases may still require an upgrade script
+
+Git docs on Tags:
+* https://git-scm.com/book/en/v2/Git-Basics-Tagging
+
+=== Branch Tags ===
+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
+{{{
+[BranchName]-[Major].[Minor].[Sub]-[BranchRelease].[Sub]
+}}}
+
+== Upgrade Scripts ==
+For every update that requires it, an Upgrade script will be added to:
+{{{
+eden/static/scripts/upgrade/1.a.b-1.a.c.py
+}}}
+The 'pull' script will be modified to call this script automatically
+
+=== Template Upgrade Scripts ===
+If there are template-specific changes for an update then these will be found in:
+{{{
+eden/modules/templates/TEMPLATE/upgrade/1.a.b-1.a.c.py
+}}}
+This will be checked for automatically by the 'pull' script
+
+=== Branch Upgrade Scripts ===
+Typically a Branch will be using a custom Template (even if this is a thin layer on top of other templates).
+
+Branch upgrade scripts will therefore be in:
+{{{
+eden/modules/templates/TEMPLATE/upgrade/1.a.b_d.e-1.a.b_d.e.py
+or
+eden/modules/templates/TEMPLATE/upgrade/1.a.b_d.e-1.a.c_d.e.py
+}}}
+This will be checked for automatically by the 'pull' script.
+
+If 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.
+
+== Old Info ==
 When making a Stable Branch from which to build releases, we need to do these tasks:
 
@@ -76 +144 @@
  * Reboot VPS (free up resources for improved performance)
 
-=== Ideas ===
+=== See Also ===
  * [http://systers.org/systers-dev/doku.php/svaksha:release_management_notes Systers release process]
  * [http://www.youtube.com/watch?v=i7pkyDUX5uM OpenBSD release process]