Release Management

This page describes the Release Management of the Metadata Management. We need the Release Management to deliver only new and tested features to a release of this product. The following image describe this process.

We are using feature branches and some other permanent branches.

Master This branch is only for the production server and has just tagged releases.

Hotfix This branch is only for hotfixes, if a critical bug was found at the production server. The fixes has to merged into the Master and Development/Release branch.

Release We will using a release branch for the last 2,5 days of our sprints. This release branch will pushed to the test server. All features will be moved into the next sprint and not to the release branch, if they are not marked as testable. It can be only one release branch active at once. If all new features were succesfully tested, the branch will be merged into the Master and Development branch. If a new version was merged into the Master branch, it will be tagged and released to the production server.

Development The development branch is primary used as a basic branch for further feature branches or release branches. Smaller Updates or changed will be commited into this branch directly. The development branch will be pushed to the test server, unless the last 2,5 days of a sprint.

Feature Branches We are using feature branches for develop bigger features/issues. The review happens in the feature branch. This branch will be merged into the development branch after a successfull review.

For further and more detailed information, take a look into this article: http://nvie.com/posts/a-successful-git-branching-model/ Please Notice: There are small differences between our Release Management and the article.