Release Process

The release process of the AAW project is based on the well known git flow branching model. A good explanation about git flow is found in http://nvie.com/posts/a-successful-git-branching-model/.

In our case, the development branch is realised in the master branch which is our main development branch. Every small fix can be directly pushed into this branch. New features or modules has to be branched of this master branch named with the feature name. Also, for every overhaul of a module, a new branch should be created. After finishing the development of these feature branches, they can be merged into the master branch.

In case of releasing AAW to the public, or doing play tests, two additional branches are used. First of all, the current development will be feature freezed and the current state will be branched into a prerelease branch. Fixes for the release are than directly pushed into this branch. For final release, this prerelease branch is merged into a release branch. After a release of AAW, the release branch will be back merged into the master branch.