Release Policy - Development Cycle

Scope

• Having passed the Planning Cycle new features can be assigned a release for development.
• This article describes the policy for the Development Cycle and its mapping to the respective status in the SOS Change Management System.

Life Cycle

Features in development will pass through the following status:

IN PROGRESS

• The feature has previously been ACCEPTED or DEFERRED within the Planning Cycle.
• The development for this feature is started. The feature is assigned a develper and a release.

RESOLVED

• The development process for the feature has been completed.
• The resolution may include
  • the feature being ready for approval, i.e. awaiting verification by an approver (resolution: fixed).
  • the feature not being fixed (resolution: won't fix).
  • the feature duplicating an issue and being resolved with that issue (resolution: duplicate)
  • the feature requirements being incomplete (resolution: incomplete).

APPROVED

• The feature has been confirmed to work by an approver.
• The feature will be included with the assigned release.

RELEASED

• The feature is available with a release.
• This constitutes the end of the Development Cycle.
• The feature might be dropped from future releases within a Deprecation Cycle.