Hi,
I want to give a small explanation about the isssue handling process if
anyone is not familar with it. I have marked important steps with a
leading "*"
-* You find a problem ( e.g. wrong string ) and file an issue. Best
practices is that you give a hint where to find the wrong string like
"New->Writer->Insert->xyz" in English and your language, key id if
available and so on. A good description reduce a lot of stress from the
developer.
-* The issue will be attached to an cws ( childworkspace ) and fixed
there. The issue status will be set by the developer to "fixed". You can
use the EIS tool to find out where this issue is attached to
http://eis.services.openoffice.org/EIS2/servlet/GuestLogon
- A build will be created from that cws
-* The bug submitter ( or anyone else except the developer ) checks that
build and set the issue to 'verified'
- The cws is set to "Ready for QA" and will be tested by the QA
- If the cws passes the QA, the cws will be "Approved by QA"
- A Program manager nominates the cws for integration into the master by
setting the cws status to "nominated"
-* The cws will be integrated into the master workspace. Use the EIS
tool to find out into with milestone the cws got integrated.
-* The issue submitter checks the next master build and set the issue to
"close" if the issue also fixed there. This second check is need as it
can happen that the fixed file haven't been commited / a cvs conflict
cause a regresssion or similar
***Important: If the issue is not fixed in the master please reopen the
issue and write a significant info into the issue!
Groetjes,
Ivo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
