← Back to team overview

neos team mailing list archive

[Blueprint docu-feature-request-workflow] (DOCU) Feature Request workflow

 

Blueprint changed by Daniel Kulesz:

Whiteboard set to:
Step 1:
The feature requester opens a new bug in the project's bug tracker on launchpad and describes his or her ideas in the bug description. The title should contain the prefix "(FR)" as first token. It should also be assigned the "feature-request" tag.

Step 2:
The project developers discuss the feature request in the bug tracker. This discussion can also involve prototyping possible solutions and arguing about in which future version the feature shall be realized.

Step 3:
After reaching a consensus, the project team appoints a drafter, who will be responsible for creating a blueprint for this feature request. This person is set in the "assigned to" field of this feature request. Also an approver, who will be responsible for the quality assurance of this feature, is elected and set.

-- 
(DOCU) Feature Request workflow
https://blueprints.launchpad.net/revager/+spec/docu-feature-request-workflow