Joerg Sievers wrote:
> Hi Matthias!
>
>
> Mathias Bauer wrote:
>> (1) While developing your feature: discuss feature with people on IRC,
>> mailing lists and whatsoever to your liking; it is *recommended* (though
>> not mandatory) to contact the project lead as early as possible and
>> discuss with QA and UserEx also (not to ask for approval but to avoid
>> problems by early contact!).
>
> Good description in the last sentence.
>
>> (2) While development happens make sure that at the end you deliver a
>> "spec". This could be just an issue in IZ, a web page or a document,
>> details can be described elsewhere. BTW: I consider having an Issue in
>> IZ mandatory as we need to have a reference for cvs commits.
>
> Be sure that your "spec" meets the 'three golden rules' which can be
> used for a review of the "specification"
>
> http://wiki.services.openoffice.org/wiki/The_Three_Golden_Rules_for_Writing_OpenOffice.org_Specifications
>> There is nothing "overweight" included and you have to look at these
> tasks otherwise the integration could (and it will, be sure) fail and
> will cost others time or break the testing, building or whatever in this
> case could happen...
I'm not so pessimistic as you are. ;-) But I agree that it helps
developers if we make them aware of possible problems that can appear
later on and how they can be avoided easily. So our rule set should
include the golden three words ("Complete","Clear","Simple") and the
link to the mentioned wiki page as a resource for explanations of the
meaning and the reason of them.
>> (3) Get necessary builds (perhaps by using build bots) and hand builds
>> and "spec" over by announcing them somewhere(we must define where!) so
>> that QA, translation and documentation can start working on it.
>
> There is already a tool how to announce feature changes:
>
> http://eis.services.openoffice.org/
>
> -> Changes mails
> -> "external" feature
> or
> -> "external" API change
At the risk of being caught ignorant: should feature/changes mails on
these lists be posted before the CWS is approved? I think that odds
aren't low that something might get changed after handing over the CWS,
especially in case of new developers.
Perhaps we can distinguish between "preliminary" and "final"
announcements, the former is sent when the CWS is handed over from the
developer, the latter when the final step ends with the CWS approval.
Ciao,
Mathias
--
Mathias Bauer - OpenOffice.org Application Framework Project Lead
Please reply to the list only, [EMAIL PROTECTED] is a spam sink.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
