neos team mailing list archive

[Daniel Kulesz <daniel.kulesz@xxxxxxxxxxxxxxxxxxxxxxxxxxx>]

I am against the idea of setting the bug status to "in progress" - we
can set this, if there is some discussion going on. But for "untouched"
feature requests, this state seems a bit misleading to me.

About the TODO-SPECIFICATION-DOCUMENTATION-RELEASE: I think the naming
is a bit misleading (sorry about that). I thought about some document,
which outlines the process of creating a new release. I think we already
have https://blueprints.launchpad.net/revager/+spec/docu-release-
checklist which covers 90% of it. (the document was not in such a state
at the time of drafting the blueprint)

I will substitute this in a minute.

-- 
(FR) We need a common standard for processing new feature requests
https://bugs.launchpad.net/bugs/494573
You received this bug notification because you are a member of Team
N.E.O.S., which is the registrant for RevAger.

Status in RevAger: In Progress

Bug description:
This bug report is for discussion of our feature request workflow (https://blueprints.launchpad.net/revager/+spec/docu-feature-request-workflow).