Scope
- Due to ongoing development features will evolve and sometimes will Feature Life Cycle Management includes that released features may eventually be replaced by different new functions.
- Therefore, features become deprecated. This article explains the procedure with which we handle this situation.
Lifecycle
Deprecated Feature
- , i.e. they are subject to a Deprecation Cycle:
- the Deprecation Cycle is performed for features that previously have been subject to a Development Cycle.
- This article describes
- the policy for handling of deprecation and minimizing the impact on users.
- the mapping to the respective status in the Change Management System.
- Further resources for life cycle management
Life Cycle
Deprecated Features will pass through the following status:
Status |
---|
colour | Blue |
---|
title | DEPRECATED |
---|
|
- Deprecation announcements will be included with Depreciation announcements are included in each release if applicable.
- Starting from the announcement the deprecated feature is still supported for the current release.
...
- Deprecated features will continue to be supported after the deprecation announcement for the lifetime of the current release.
- The resolution is set to
deprecated
.
Status |
---|
| |
---|
colour | Blue |
---|
title | UNSUPPORTED |
---|
|
- End of support announcements are will be included with each release if applicable.
- With the following current release a previously deprecated feature becomes an unsupported feature, i.e. should problems occur then they will not be fixed.
- The functionality is still usable.
...
- The resolution is set to
deprecated
.
- Feature removal announcements are will be included with each release if applicable.
- Later release will remove Prevously unsupported features . Removalare 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.
- A subsequent This feature will then be announced as being unsupported from release 1.9 will declare this feature being unsupported:
- This feature will still be included in all maintenance releases1releases 1.9.1, 1.9.2 etc.
- No support is provided should Support will not be provided if an unsupported feature should break in a release 1.9 or later
- A This feature may be removed in a subsequent release such as 1.10 or later may remove this feature.
- Please note:
- The period between releases will usually be around three months
Explanation- Between releases usually about three months will pass.
- This means that you will have about six months time to modify you your configuration and to upgrade to replacement features.
...