Hi Maho,
Le 30 juin 08 à 02:17, Maho NAKATA a écrit :
From: Pavel_Janík <[EMAIL PROTECTED]>
Subject: Re: [mac] DEV300_m21 has been provided Re: [mac] [Intel]
[Leopard] Frequent crashes
Date: Sat, 28 Jun 2008 08:16:27 +0200
I think Eric's main problem is that you "spam" (read: you announce
too often ;-) releases and other lists with it...
What Pavel says defeintely right, and this is what I think.
Thanks!
That's strange, I cannot say myself what I think :-) FYI, the answer
is : no, no and no.
BTW, can you please stop to writing wrong assertions about me ? Thanks.
My role is just providing builds for MacOSX. That's all.
Please add: working builds.
If there are serious problems please let me know or fix ASAP!
There are several problems discovered, and concerning *the
development*, not the releases.
We posted several mails with "crash" in the subject. Impossible to
miss them if you are subscribed to this list.
Anopther point I see :
Some people (say Team B) are doing intensive QA, say two times a
year. While another one (say Team A) is doing continuous QA ( ~near
to every day) ...
IMHO, it needs to be analized too.
Please write e-mails with issue numbers - or - providing a URI
which querying IssueTracker; e.g. P1/P2, MacOSX, aqua etc.
This is very good excersize for QA person.
We have enough to do with development, thanks :)
Again, the issues have been discovered (and discussed here) in the
development phasis, not at release time.
That's the reason why thoses milestones should not have been proposed
to the public, and I would like to find a solution concerning what
can be public.
Last, I don't see why provide less public builds is a problem ?
Regards,
Eric Bachard
--
qɔᴉɹə
