On 3/19/07, Maho NAKATA <[EMAIL PROTECTED]> wrote:
From: Caio Tiago Oliveira <[EMAIL PROTECTED]>
Subject: Re: [qa-dev] Automated GUI Testing: What is a 'global' CWS and how do
we test it?
Date: Mon, 19 Mar 2007 02:48:50 -0300
> I'm not requesting Sun QA'ing for Mac OS X, I'm just requesting the
> nomination process should take into account the QA results for Mac OS X
> if someone (from the community or a volunteer from Sun) does the job.
Okay. Assume you found some defects in a cws marked or ready for QA.
Then communicate with QA representable or/and members who has a commit
right to ask for integration of your patches. If rejected this might be a
problem. I belive this is not the case.
After marked as ready for QA, it depends. IMHO, once global cws
is `approved by QA' it is very hard to back to the status to `new'.
It wastes the time and resouce of Hamburg QA team.
As Jogi wrote, this is a hard task.
If you have objection for this process, then, MacOSX must be a supported
platform for nomination process. Please ask othres (Hamburg RE)
to implement it.
No. It wouldn't be marked as approved, since it shouldn't.
The issues should be found on the timeline for the QA process.
BTW: can somone forward a message from EIS when a created cws are global one
to warn other porters to check porting issues?
> From my point of view, for everything I've read about it: a CWS should
> not introduce new issues.
I agree. But for which platforms? You may want to add MacOSX here.
Yes and maybe others on the future (if shown maturity enough).
> Are you saying that Mac OS X, FreeBSD and everything other than GNU
> Linux/Windows/Solaris should stay forever as second class platforms,
> regardless their maturity level?
This is what I cannot decide. This is what the Hamburg RE can decide.
However, I think - it is very good idea to restrict primary platforms as
Windows/GNU/Linux and Solaris.
Of course, if resouce is available, +1 for MacOSX.
[...]
Still have a question?
But saying to the people porting OOo that the project won't care to
its breakage only because Sun doesn't want to support them is not
good.
I'm not proposing to change anything inside Sun. EIS is inside OOo,
the community cares. The process is for the OOo development.
So... if we got a Mac RE team, why would someone object?
I expect a "no" from Sun, but not from the community.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
