User Tools

Site Tools


content:servalmesh:release:main_page

This is an old revision of the document!


Release procedure

These are the procedures used to publicly release new versions of the Serval Mesh app for Android.

Standard release

To make a new release:

  1. Choose a new version number, denoted X.Y in this procedure
  2. If the candidate test fails, then either:
  3. If the candidate passes all tests, then:
  4. If the final test fails, then either:
  5. If the final build passes all tests, Publish the final build

Bugfix release

A bug fix is a minor change to a recent release intended to correct one or a few serious problems that were not detected by beta testing. A bug fix does not introduce new functionality, except as needed for users to work around to a serious problem. A bug fix does not warrant a new release number, but does warrant release candidate testing.

To make a bug fix release:

  1. Increment the bugfix number, giving a version number of X.Y.B
  2. Continue from step 3 of the standard procedure (above)

Hotfix release

A hot fix is a bug fix that does not introduce any new functionality or any new mode of failure. Only a senior developer is qualified to make this judgement. It generally involves changing only one or a few lines of source code to correct a logic error or omission. A hotfix release skips the release candidate testing, and relies only on the fixer's own casual testing and the final release test to ensure quality.

To make a hot fix release:

  1. Increment the bugfix number, giving a version number of X.Y.B
  2. Continue from step 7 of the standard procedure (above)
content/servalmesh/release/main_page.1377068727.txt.gz · Last modified: 21/08/2013 00:05 by Andrew Bettison