Release Process

This page describes how we use branches and tags with every new release.

Note: A X.Y.Z versioning scheme is utilized, where X is the major version (such as the initial public release, major revisions, etc), Y is the minor version (such as the application's state after completing a milestone), and Z is the patch version.

1. When the milestone is started, a milestone plan is created.
2. Features from the milestone plan will be continuously merged and tested in the master branch.
3. When the milestone is complete, a release branch is created: release/X.Y.
4. Flowthru will be thoroughly tested from that branch. Any critical issues should have fixed delivered to release/X.Y.
5. When there are no more additional critical issues, release/X.Y is merged into master.
6. A release tag X.Y.0 is created and is deployed.
7. Any further patches should be committed to the release/X.Y branch and patch versions should be used: X.Y.1, X.Y.2, etc.