Hi Bernd,
> If you want a formal process than I would propose to get the following
> into QA processes:
>
> Don´t nominate a CWS if tinderbox status is red without checking
> together with the owner first if it´s OK that the status is red.
The QA rules [1] should be changes only, when the developer (owner of
a CWS) knows, what to do, when the CWS is rejected. So for all teams
a definition or a process have to be defined for this new tooling.
That is what I miss.
> I do believe a rule to not nominate when known to break on a platform
> already is there in our processes, is it?
The QA couldn't check this until now. The QA representative gets an
install set and for Sun internal patches. It is required to get builds
on 2 platforms. If one of the other platform is broken, nobody take care
until now. And especially for Mac. Sun internally we do not test Mac, so
how should be take care of this.
Thorsten
[1] : http://wiki.services.openoffice.org/wiki/Approve_a_CWS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
