Hi Christoph, On Thu, May 26, 2005 at 06:08:42PM +0200, Christoph wrote: > [...] > I am newbie in the OpenOffice.org project. I have a focus on software > engineering and there I am interested in QA. At the moment I try to > understand the specified processes of contributing to OpenOffice.org. > [...] > 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.
Depending on how you use the issue while creating the specification... If you add a lots of comments regarding the development of the specification, then it is a good idea to file a seperate issue (for brevity, to make it easier to read the issue). If you don't use the issue to discuss the specification, then you can use the same issue for the implementation as well. But most of the time you'll need several issues anyway (one for the documentation, one for the implementation itself, maybe one for l10n) > 2. Is it mandatory to write a specification? As far as I understand it, it > is not mandatory. I strongly suggest to write a specification. Depending on the impact of the feature a specification is necessary. (If more than two people have to deal with the feature, you'd better write one).. Suggested reading: http://jimmac.musichall.cz/weblog.php/Design/Speccing http://www.joelonsoftware.com/articles/fog0000000036.html ciao Christian -- NP: Raging Speedhorn - Knives And Faces --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
