Date: Thu, 28 Mar 2024 21:48:56 +0000 (UTC)
Message-ID: <1404443392.12015.1711662536901@change.sos-berlin.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_12014_1567491629.1711662536900"
------=_Part_12014_1567491629.1711662536900
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Release Policy - Development Cycle
Release Policy - Development Cycle
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 developme=
nt.
- after releasing within the Development Cycle a feature might be dropped=
from future releases within a Deprecation Cycle.
- This article describes
- Further resources for life cycle management
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 as=
signed a developer and a release.
RESOLVED
- The development process for the feature or bug-fix has been completed.<=
/li>
- The resolution states
- the issue being ready for approval, i.e. awaiting verificati=
on by an approver (resolution:
fixed
).
APPROVED
- The issue has been confirmed to work by an approver.<=
/li>
- 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.
------=_Part_12014_1567491629.1711662536900--