Hey,
I am glad that I read the QA list ... :-) So, I just found out, that
since Bernds mail, changes in a CWS need to be Tinderbox compatible.
Mhhhhmm, ->Bernd, change acceptance isn't your biggest strength, is it?
(No flame intended, I promise you a beer if you are offended :-)
But, even after I have read the mails, I am not sure how to work with
this respectively to avoid build breakers in practical life. E.g. I just
set my latest CWS to "Ready for QA", despite the MacOSX being red. I had
somewhat a of clue what went wrong, but was not really able to fix it,
as I had no machine at hand. So, my question is, what is the suggested
approach to address such issues? I currently see three options:
-a- ignore it, does not seem to be choice
-b- find somebody e.g. with a Mac and ask him/her to look at the problem
-c- write an issue for the Mac port owner
IMHO, none of these options are suitable for practical life. The only
real solution (which needs to scale well) I scan see is, to provide
access e.g. to Macs, to allow a developer to fix the issue him-/herself.
By the way, it would be nice, to offer a buttom to retrigger tinderbox
builds, and certainly a buildbot would be nice as well.
And, as the tinderbox stuff seems to be important, I would have at least
expected a discussion on [email protected], as this affects all OOo
developers ...
Regards
Kay
Thorsten Ziehm wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
