Milestones - HMS-Analytical-Software/SASUnit GitHub Wiki

A milestone is a timeframe for the completion of a set of requirements or a set of task assignments.
There are ordinary milestones for requirements and developer milestones for task assignments, the latter being only necessary for complex releases.
For simple releases, ordinary milestones also can be used for task assignments.

Milestone names follow this convention:

  • ordinary milestones:
    v<major release>.<minor release> or v<major release>.<minor release>.<fix no.>, where <fix no.> is being used for quick fixes to recent releases. The numbering of releases starts with 1 and the frequency of increment is decided by project managers. An example is v2.1 or v2.1.1 for the first quick fix for version 2.1.
  • development milestones:
    d<major release>.<minor release>.<number> where <number> is a consecutive numbering of development milestones per minor release.
  • non-release milestones:
    It should be possible to have milestones not attached to any SASUnit release.
    Changes to GitHub workflows or documentation can be aggregated here.

Milestones are being assigned to tickets as part of the ticket workflow.


Back to Release Management Guidelines.

⚠️ **GitHub.com Fallback** ⚠️