Hello Christoph,
first of all it might be valuable to understand the current process how
features get into the product. Please take some minutes and read
following document:
http://qa.openoffice.org/issue_handling/handling_RFEs.html
Somebody who implements (from the developers perspective) a feature
needs to document how the implementation is planned, documented, QA'ed,
if it's accessible and so on. A specification is a document that
describes the feature. From the 'issue' perspective features can be
implemented by having one issue which tracks it's implementation but it
can have several issues as well (spec issue, implementation issues
[which describe an implementation detail], qa issues [for manual
testing, API testing, GUI automation], documentation issue[s], etc.)
If you're interested into details then please take a look at the 'specs'
project at http://specs.openoffice.org
At the end of that page you can find a specification template and a
specification guide.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
