Hi Christoph, > 1. If I want to write a specification for a new feature I have to do that by > creating a new issue. Will the later implementation of this specification > run under the same issue number or do I have to create a new issue for the > coding part.
For "normal" issues, there is a rule to not mix different things into one issue, for various reasons (http://qa.openoffice.org/issue_handling/basic_rules.html#one_per_issue). I would keep it the same way for specifications/features: Let one issue focus on one facet of the problem: Specification, Localization, Implementation, QA, whatever. This makes working with the issues much easier. > 2. Is it mandatory to write a specification? As far as I understand it, it > is not mandatory. Christian already gave some good links, and I heartly agree to his "you better do" suggestion. One thing to keep in mind is that you need to discuss your feature with other parties (the project owner, probably the user experience team, other core hackers to check for side effects of the feature, and so on), which is much easier if you have a document to talk about, instead of a long issue with partly obsoleted discussion. Ciao Frank -- - Frank Sch�nheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
