User Tools

Site Tools


content:servalmesh:release:main_page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
content:servalmesh:release:main_page [21/08/2013 00:07]
Andrew Bettison [Standard release]
content:servalmesh:release:main_page [25/08/2013 18:52] (current)
Andrew Bettison add "Prepare for release" step
Line 2: Line 2:
  
 These are the procedures used to publicly release new versions of the [[:content:servalmesh:]] app for Android. These are the procedures used to publicly release new versions of the [[:content:servalmesh:]] app for Android.
 +
 +
 +You can [[discover the release status]] at any stage during development or release, to find out if a release is in progress, and if so, what stage it is at.
  
 ==== Standard release ==== ==== Standard release ====
  
-To make a new release:+Leading up to the release, the following work should be done: 
 + 
 +  - [[Prepare for release]] 
 + 
 +Once the code is ready for release, the following procedure should be followed within a short time frame (a few days):
  
   - [[Choose a new version number]], denoted **X.Y** in this procedure   - [[Choose a new version number]], denoted **X.Y** in this procedure
   - [[Start the standard release process]]   - [[Start the standard release process]]
-  - [[Prepare a release candidate]]+  - [[Build a release candidate]]
   - [[Test the release candidate]]   - [[Test the release candidate]]
   - If the candidate fails any test, then either:   - If the candidate fails any test, then either:
-    * [[Fix the release candidate]] and repeat from step 3, or+    * [[Fix the release]] and repeat from **step 3** (make a new release candidate), or
     * [[Abandon the release]]     * [[Abandon the release]]
   - If the candidate passes all tests, then:   - If the candidate passes all tests, then:
Line 18: Line 25:
   - [[Test the final build]]   - [[Test the final build]]
   - If the final build fails any test, then either:   - If the final build fails any test, then either:
-    * Fix the problem and repeat from step 2, or+    * [[Fix the release]] and repeat from **step 3** (make new release candidate), or
     * [[Abandon the release]]     * [[Abandon the release]]
   - If the final build passes all tests, [[Publish the final build]]   - If the final build passes all tests, [[Publish the final build]]
 +  - [[Finish the release process]]
   - [[Update the Wiki]]   - [[Update the Wiki]]
   - [[Announce the release]]   - [[Announce the release]]
Line 33: Line 41:
   - [[Start the bugfix release process]]   - [[Start the bugfix release process]]
   - [[Commit code changes to the bugfix branch]]   - [[Commit code changes to the bugfix branch]]
-  - [[Prepare a bugfix release candidate]] +  - Continue from **step 3** of the standard procedure (make a release candidate)
-  - Continue from step 3 of the standard procedure (above)+
  
 ==== Hotfix release ==== ==== Hotfix release ====
Line 44: Line 51:
   - [[Increment the bugfix number]], giving a version number of **X.Y.B**   - [[Increment the bugfix number]], giving a version number of **X.Y.B**
   - [[Start the bugfix release process]]   - [[Start the bugfix release process]]
-  - [[Make code changes to the bugfix branch]] +  - [[Commit code changes to the bugfix branch]] 
-  - Continue from step 7 of the standard procedure (above)+  - Continue from **step 7** of the standard procedure (build the final release)
  
  
content/servalmesh/release/main_page.1377068876.txt.gz · Last modified: 21/08/2013 00:07 by Andrew Bettison