Release Management

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

We are using feature branches and some other permanent branches.

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

Hotfix These branches are only for hotfixes, if a critical bug was found at the production server. The fixes have to be merged into the Master and Development/Release branch.

Release We use a release branch for the last 2,5 days of our sprints. This release branch will be deployed to the test server. All features are 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 changes 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 developing 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 blog post: https://t3n.de/news/git-workflows-zusammenarbeit-1095433

Please Notice: There might be small differences between our Release Management and the blog post.