Scope
- Feature Life Cycle Management includes that planned features are subjec to a Development Cycle:
- having passed the Planning Cycle new features can be assigned a release for development.
- after releasing within the Development Cycle a feature might be dropped from future releases within a Deprecation Cycle.
- This article describes
- the policy for developing features.
- the mapping to the respective status in the Change Management System.
- Further resources for life cycle management
- for the overall Product Life Cycle see Release Policy - Product Life Cycle Management
- for information about release availability and maintenance see Release Policy - Platform availability and support
Life Cycle
Features in development will pass through the following status:
IN PROGRESS
- The issue has previously been ACCEPTED or DEFERRED within the Planning Cycle.
- The development for this feature or bug-fix is started. The issue is assigned a develper and a release.
RESOLVED
- The development process for the feature or bug-fix has been completed.
- The resolution may include
- the issue being ready for approval, i.e. awaiting verification by an approver (resolution:
fixed). - the issue not being fixed (resolution:
won't fix).
- the issue being ready for approval, i.e. awaiting verification by an approver (resolution:
APPROVED
- The issue has been confirmed to work by an approver.
- The issue will be included with the assigned releases.
RELEASED
- The feature or bug-fix 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.