2007/6/26, Tim Ellison <[EMAIL PROTECTED]>:
Stepan Mishura wrote:
> On 6/26/07, Tim Ellison <[EMAIL PROTECTED]> wrote:
>> Mikhail Loenko wrote:
>> > We have fixed regression in beans and will build one more snapshot.
>> >
>> > Anything else identified as "to be fixed in M2"?
>>
>> I think we are still investigating some potential fixes, like StrictMath
>> and more in Beans; and there are some longer running tests still going
>> (at least I don't remember seeing Tatyana's results).
>>
>
> How log we should be open for 'the last fix in M2'?
As long as it takes to get a stable build.
We won't fix all the known bugs, so what is the definition of "stable build"?
I guess we should not have regressions from M1 and we'd better not have
regressions introduced by recent commits. Anything else?
Thanks,
Mikhail
> May be it makes sense to start testing cycle with new milestone
> candidate. And if we get investigation results in short time we can
> interrupt testing, commit required fixes and start from the beginning.
The fixes that have gone into the current candidate should not affect
the ongoing testing, otherwise we would stop early and respin the build.
If you have spare cycles to do more testing then maybe you could test
the current candidate some more. I think that would of greater value
than overlapping the same tests on a new candidate that will be
essentially the same.
Regards,
Tim
