...
| Status | ||||
|---|---|---|---|---|
|
- This is not a feature, it is a known issue and will by purpose not be changed.
- Known Issue is an end status, there is no further decision taken
- There is no feature to discuss
- ...
| Status | ||||||
|---|---|---|---|---|---|---|
|
- The feature has to be first discussed before a further state is decided
- The feature can be then dismissed or accepted.
| Status | ||||||
|---|---|---|---|---|---|---|
|
| Status | ||||||
|---|---|---|---|---|---|---|
|
- Feature removal announcements will be included with each release if applicable.
- Unsupported features may be completely removed from future releases.
...
- In case the feature is NOT going to be implemented, it will be set to Dismissed.
- Dismissed is an end status, there is no further decision taken.
- In case the feature is going to be implemented, it will be set to Accepted.
- At that point, the Development of the feature can be initiated.
| Status | ||||||
|---|---|---|---|---|---|---|
|
- The feature is going to be developed because it has been Accepted
- Even though, the feature is not going to be developed for the Planned Release.
- Another future Release will be assigned to it in order for this feature to be developed.
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.
...