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...
(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
Then you will find your announcement in [email protected] and
also the QA, DOC etc. will able to find it.
- The wording in the menu sould be changed because they have been used
1:1 from Sun's EIS
- The announcement can also be written manually but the needed
information maybe is missing then...
Cu,
Jogi
--
===============================================================
Sun Microsystems GmbH Joerg Sievers
20097 Hamburg Quality Assurance Engineer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
