Manage the versions

A sprint is composed of some issues and developments related to these issues compose a release.

All developers need to fork the project to contribute to it. It's important to get ONE development for ONE issue to keep a simple version managing.

The process to implement a development

1. Create a new branch from the develop branch on the developer's repository
2. Develop the fix or the new feature on this branch
3. Create a pull request on the develop branch of the project repository
4. A developer has to review the developed code to accept or to refuse the pull request
5. If the pull request is accepted, the development is merged on develop / If the pull request is refused, the development is not merged

Create a release

It is said previously, a release corresponds to a group of developments on develop which will be merge into master.

1. After validation of all tests on develop for the developments implemented, create the branch release/X.X.X from the develop branch (X.X.X is the version number)
2. Create a milestone with the name release/X.X.X
3. Add the milestone on all issues related to this release
4. Create a special pull request to merge into master
5. After the merge, close all issues related to the release (it is possible to close all issues related to a milestone) and close the release project
6. Create a tag (click on the button Draft a new release on this page) on master for the new release TODO