Changes between Version 9 and Version 10 of AdminReleaseManagement

Timestamp:

Apr 12, 2017, 2:35:03 PM (8 years ago)

Author:

davea

Comment:

--

AdminReleaseManagement

@@ -26 +26 @@
 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.
+
 So the overall release management cycle is:
 
@@ -51 +56 @@
     * update doc/versions.inc
     * email the Alpha testers again (tell them to test the new release).
-* At some point you'll have a version with no major bugs and > 90% test coverage,
+* At some point we'll have a version with no major bugs and > 90% test coverage,
   and it can become the new recommended release.
     * update the client version in the code to an even minor version, release 1.
@@ -58 +63 @@
     * update doc/versions.inc
     * update boinc_alpha/test.inc and email the Alpha testers saying they're done for now.
+    * Upload the Android package to the Google and Amazon playstores.  TODO: how do we do this?
 
 == Updating client version ==