Release Process

The branching model (GitFlow) describes the various branches. An overview of the release process is as follows:

1. Create the release branch.
2. Ensure the Stable CI's build number corresponds to the desired semantic version (see Incrementing the Version Number).
3. Either perform a commit or manually trigger a Stable CI build to generate the build artifact.
4. Test the build artifact (Test Inventory).
5. Commit any fixes to the release branch and repeat steps 3-5 until release quality is achieved.
6. Merge the release branch to master and develop.
7. Delete the release branch:
   • git branch -d release-x.x
   • git push origin :release-x.x
8. Create the GitHub release:
   • Specify a tag against master using the part of the semantic version preceding the plus sign, e.g. v1.0.0-beta
   • Specify a release title matching the tag name.
   • Populate the release notes as desired.
   • Attach the build artifact (must be the one generated from the build system, which was tested).
     • GitHub replaces the + with a .. Replace the . with a _.
9. Update gh-pages branch with any new information or screenshots or direct download links.
10. Update announcement posts:
    • Litecointalk
    • Bitcointalk
    • Reddit

Incrementing the Version Number

Places to modify to bump the version number correctly:

1. MiningController CI (Stable) - do this before building a release branch
   1. General -> Build version format
   2. Environment -> Install script -> $semVer
2. MiningController CI (Unstable) - after creating a release, bump the {Minor} by 1
   1. General -> Build version format
   2. Environment -> Install script -> $semVer