These are the procedures used to publicly release new versions of the Serval Mesh 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.

1. Choose a new version number, denoted X.Y in this procedure
2. Start the standard release process
3. Build a release candidate
4. Test the release candidate
5. If the candidate fails any test, then either:
   • Fix the release and repeat from step 3 (make a new release candidate), or
   • Abandon the release
6. If the candidate passes all tests, then:
7. Build the final release
8. Test the final build
9. If the final build fails any test, then either:
   • Fix the release and repeat from step 3 (make new release candidate), or
   • Abandon the release
10. If the final build passes all tests, Publish the final build
11. Finish the release process
12. Update the Wiki
13. Announce the 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. Start the bugfix release process
3. Commit code changes to the bugfix branch
4. Continue from step 3 of the standard procedure (make a release candidate)

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. Start the bugfix release process
3. Commit code changes to the bugfix branch
4. Continue from step 7 of the standard procedure (build the final release)