Versions cycle

Each sprint should have its own version number.

Sigmah follows a x.y.z version scheme:

At the end of a sprint, result should be released as release candidate (rc). If the release candidate version if rejected, a new release candidate version has to delivered. And this processe loops until a release candidate is accepted.

At the end of the process, when the release candidate is accepted, the software is released a last time with the final release number (without “rc*” in its version number), and the source code repository is tagged with the final version number as well.

In the issue tracker, release candidates are not followed independently, and all tickets must be attached to the full version number associated with the sprint, not to the release candidate one.

Typical scenario