Mark Phippard wrote:
> On Thu, Apr 10, 2008 at 10:02 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>> Yeah, same here. It's pretty obvious that RC1 isn't likely to get much
>> more testing -- these things happen in bursts, and (as Paul noted elsewhere
>> in his mail) RC1 isn't even publicly released yet. Most of the developer
>> testing done to sign a release involves strict use of the test suite. This
>> burst of additional issues at all was the result of adhoc testing. So, if
>> the goal is ride the statistical wave of find-rates today, we need to
>> actually get the code into more people's hands. And to do that requires
>> actually releasing something. It ain't RC1 though, because we now know
>> without a doubt that that snapshot is *not* a potential candidate for
>> release.
>>
>> +1 on an RC2, shooting for, perhaps, Monday morning, first thing?
>
> If you mean have it signed and released to the public for then, +1.
>
> Otherwise, is there a specific reason to wait until then? Perhaps
> there is some fix activity going on that I am just not aware of.
Oh, I would have said "Friday at noon" but for the distinct feeling that,
given the options of the weekend being used either finding and fixing bugs
or testing and signing tarballs, most folks would probably rather spend
their time finding and fixing bugs, and we'd all be signing tarballs on
Monday anyway. :-)
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-04-10 19:48:11 CEST