GitLab

This is our first milestone; from now on, we'll organize our tasks through out milestone fortnightly.

The team will discuss priorities and number of tasks that should be in the milestone, a number of tasks that is feasible. Remember all those tasks must be complete in the milestone (fortnightly).

Nomenclature of the milestone title:

• v tag meaning version we wish to release.
• 1.x.x-x major version, means all the futures should be compatible with this version, when we increase the major (e.g. 2.1.1-1), there is no compatibility with previous version (e.g. 1.2.3-1).
• x.0.x-x minor version, new futures has been introduced.
• x.x.0-x patch, bug fixes, no new features, just bug fixes.
• x.x.x-0 number of the sprint, which controls how many sprint we used to released such a version.

At each release we must generate a tag from the master branch, with the nomenclature above.

We will follow the git workflow as on the figure below: