Date: Fri, 29 Mar 2024 11:57:51 +0000 (UTC)
Message-ID: <1976198812.12839.1711713471523@change.sos-berlin.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_12838_1707905602.1711713471523"
------=_Part_12838_1707905602.1711713471523
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Release Policy - Deprecation Cycle
Release Policy - Deprecation Cycle
Scope
- Feature Life Cycle Management includes that released features may even=
tually be replaced by new functions, i.e. they are subject to a Deprecation=
Cycle:
- the Deprecation Cycle is performed for features that previously have be=
en subject to a Development Cycle.
- This article describes
- the policy for handling of deprecation and minimizing the impact on use=
rs.
- the mapping to the respective status in the Change M=
anagement System.
- Further resources for life cycle management
Life Cycle
Deprecated Features wil=
l pass through the following status:
DEPRECATED
- Deprecation announcements will be included with each release if applica=
ble.
- Deprecated features will continue to be supported after the deprecation=
announcement for the lifetime of the current release.
- The resolution is set to
deprecated
.
UNSUPPORTED
- End of support announcements will be included with each release if appl=
icable.
- With the current release a previously deprecated feature becomes an uns=
upported feature, i.e. should problems occur then they will not be fixed.=
li>
- The functionality is still usable.
- The resolution is set to
deprecated
.
REMOVED
- Feature removal announcements will be included with each release if app=
licable.
- Prevously unsupported features are removed from the current release.
- The resolution is set to
deprecated
.
Example
- Lifecycle
- A feature is announced as being deprecated with release 1.8:
- This feature will still be included in all maintenance releases1.8.1, 1=
.8.2 etc.
- This feature will then be announced as being unsupported from release 1=
.9:
- This feature will still be included in all maintenance releases 1.9.1, =
1.9.2 etc.
- Support will not be provided if an unsupported feature should break in =
a release 1.9 or later
- This feature may be removed in a subsequent release such as 1.10 or lat=
er.
- Please note:
- The period between releases will usually be around three months.
- This means that you will have about six months time to modify your conf=
iguration and to upgrade to replacement features.
------=_Part_12838_1707905602.1711713471523--