Page History

Scope

• Feature Life Cycle Management includes that planned features are subject 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
  New Features are going to be developed for the next Release
  • .
• This article describes our
  • the policy for
  handling this situation and its mapping with the states in the SOS
  • 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 development will pass through the following statesstatus:

Status
colour Yellow title IN PROGRESS

• The feature was previously Acceptedissue has previously been ACCEPTED or DEFERRED within the Planning Cycle.
• The Development development for this feature has already started.or bug-fix is started. The issue is assigned a developer and a release.

Status
colour Green title RESOLVED

• The development process for this the feature has finishedor bug-fix has been completed.
• The resolution states
  • the issue being ready for approval, i.e. awaiting verification by an approver (resolution: fixed).
  A resolution has been taken, and it is awaiting verification by a reporter. 

Status
colour Green title APPROVED

• Feature The issue has been confirmed and the feature is ready for releaseto work by an approver.
• The feature issue will be included in with the next releaseassigned releases.

Status
colour Green title RELEASED

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