This Plugin is under current development. To reach a permanently high quality standard we defined a development, testing and release cycle based on the git flow pattern. [Here](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) you can get further information to get a deeper understanding of git flow and it's idea.
This Plugin is under current development. To reach a permanently high quality standard we defined a development, testing and release cycle based on the git flow pattern. [Here](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) you can get further information to get a deeper understanding of git flow and it's idea.
The development tasks under git flow are separated into different types:
The development tasks under git flow are separated into different types:
* Feature
* Master
* Release
* Bugfix
* Hotfix
* Hotfix
* Release
* Develop
* Feature
#### Master Branch
The master Branch always represents the latest stable version of the plugin.
#### Hotfix
Bugs are categorized in different stages based on his priority:
* Blocker - Checkout affected: This kind of bugs will be fixed as soon as possible and will lead into a hotfix
* Critical - Main funtionality affected: This kind of bug will be fixed as soon as possible but might not directly lead into a hotfix
* Regular - Minor functionality and/or special szenario: This kind of bug will also be fixed as soon as possible but might stand behind other fixes with a higher priority.
A hotfix will appear everytime a critical bug has been reported.
