Changes between Version 11 and Version 12 of AdminReleaseManagement

Timestamp:

Jun 20, 2017, 1:02:34 PM (7 years ago)

Author:

davea

Comment:

--

AdminReleaseManagement

@@ -24 +24 @@
 The client version is bumped to 7.8 when the version is promoted to recommended.
 
-The version # is stored in boinc/version.h.
-
 In general we try to synchronize releases for all platforms (Win, Mac, Linux, Android).
 If there is a show-stopper issue that affects only one platform,
 we can test and release a fix, with a new release #.
-We'd then skip that release# for the other platforms.
+We'd then skip that release # for the other platforms.
 
 So the overall release management cycle is:
@@ -37 +35 @@
    and the client seems to be stable, create a test branch.
    This involves:
-    * create a branch as described above
+    * create a release candidate branch:
       * Tortoise Git: create branch
       * Git Push / check push all branches
@@ -45 +43 @@
         * /: configure.ac, version.h, version.h.in, version.log
         * in version.h, version.h.in: comment out pre-release with C syntax
-        * android: TODO; Oliver: textual representation, numberical value (increment)
+        * android: TODO; Oliver: textual representation, numerical value (increment)
           in 7.6, it's 146, so use 147
       * commit
       * create tag client_release/7.8/7.8.0
       * git push, check "include tags"
-    * tag the branch with a tag of the form client_release/7.8/7.7.2
     * create new translation templates (locale/update_templates.sh) and move to transifex.
     * make and upload to isaac installers for the new version.
@@ -77 +74 @@
     * Upload the Android package to the Google and Amazon playstores.  TODO: how do we do this?
 
-== Updating client version ==
-
-Update the version numbers in
- * configure.ac and version.h.in (for Unix)
- * version.h (for Win)
- * android/BOINC/AndroidManifest.xml (for Android)
-
-== Creating a branch ==
-You can do this in Tortoise Git using the "create branch" menu item,
-and committing it to the Github repo.
-
-On the commandline use: ''git checkout -b NEW_BRANCH''
-
-Creating tags: On the commandline use: ''git tag TAGNAME''
-
 == Backporting changes ==