Hi,

1. I don't know how en-US version for SUN providing RC
packages are approved (I mean I'm not in charge of this),
but I'm very sure that we (outside of Hamburg team) shoud
not touch them. If you see some problems, raise issues in the RC phase prior is better.

in the past there were more QA members involved into the release of en-US builds (eg. Mechtilde Stehmann or James McKenzie). There's no reason not to touch them. Volunteers are always welcome.

Attend Release meeting and explain why you think this is a stopper, and
have discussions.

2. en-US packages by non-SUN: up to porting team. e.g., MacOSX PPC, FreeBSD, OS/2 etc,
it is up porting team and their responsibilities.

That's true.


3. each localized packages: up to each native lang team. We (Joost and Maho; QA project co-lead
and lead) have same opinion about it.
http://qa.openoffice.org/servlets/ReadMsg?list=dev&msgNo=11125
It's up to each native language team which build they want to have distributed. As a Sun employee I just can solicit the use of the Sun provided builds.
I'm not a Sun empolyee, and I respect Joost's opinion.

My opinion, as the project lead of ja project and the QA delegate of Ja version:
I don't do actual QA tests, therefore, it is up to testers.
If testers find SUN version is good, I approve it.
if testers find other builds are good, I approve it.
If both are QA'ed without problem, I respect Joost's opinion; ask Joost to upload SUN version. If only other builds are approved,
I ask Joost to upload non SUN version.

As long as somebody had a look at that version and did tests then this is OK. I have to trust those people who provide the distribution request.


Joost and all please trust me. I never say "my build is superior"
in Japanese or English and everywhere! If someone say so, I'm hijacked :)


don't panic....

Joost

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to