Scope
- New Features might be developed and included in next Releases - these Features need to be planned
- This article describes our policy for handling this situation and its mapping with the states in JIRA.
Life Cycle
Planned features will pass through the following states:
Open
- A feature has been described and assigned
- The next step will be to decide, whether the feature is a Known Issue or it has to be Clarified.
Clarify
- Clarify means, the feature has to be discussed before a further decision is taken.
- The functionality is still usable.
Dismissed, Accepted or Known Issue
- Feature removal announcements will be included with each release if applicable.
- Unsupported features may be completely removed from future releases.
Deferred (from Accepted)
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 later.
- A feature is announced as being deprecated with release 1.8:
- Please note:
- The period between releases will usually be around three months.
- This means that you will have about six months to modify your configuration and to upgrade to replacement features.