...
Status | ||||||
---|---|---|---|---|---|---|
|
- A feature or bug has been added but might not yet be assigned to any developer or release.
- The next step will be to CLARIFY the feature, i.e. to collect requirements and to decide on future development.
Status | ||||||
---|---|---|---|---|---|---|
|
- The feature or bug has to be specified before any further status is assigned. This includes to check the validity of requirements and the feasibility.
- Subsequent to clarification the feature will then be ACCEPTED or DEFERRED for development, or it will be DISMISSED or classified as KNOWN ISSUE without further action.
Status | ||||
---|---|---|---|---|
|
- The feature or bug is classified as a known issue, i.e. as an inconvenience with a valid workaround available, and will by purpose not be changed.
- Being a known issue is an end status for a feature, therefore no further action will be taken.
Status | ||||||
---|---|---|---|---|---|---|
|
- The feature or bug is dismissed, e.g. due to architectural constraints or invalid requirements. The feature is not considered for future development.
- Being dismissed is an end status for a feature, therefore no further action will be taken.
Status | ||||||
---|---|---|---|---|---|---|
|
- The feature or bug includes valid requirements and is accepted for development with the assigned release.
- Subsequently the feature will proceed through the Development Cycle, see Release Policy - Development Cycle.
...