30 May
2011
30 May
'11
9:26 a.m.
On May 30, 2011, at 9:14 AM, Denis Gervalle wrote:
I follow Thomas and Vincent on this.
We should not hustled the release just to be on schedule.
I didn't say this ;)
We need to be on schedule and do time boxing.
Same as Thomas, I agree about rollbacking stuff that break tests. Committers should never
break tests or if they do they need to fix that immediately and not wait several days.
Since we know we have some stabilization issues it's also good to do what Caleb has
started, ie start the stabilization a few days before the release and monitor commits and
roll them back if they break anything, possibly even branch at that time to isolate the
release to come.
Thanks
-Vincent
Denis
On Thu, May 26, 2011 at 14:44, Caleb James DeLisle <calebdelisle(a)lavabit.com
wrote:
>
>
> On 05/26/2011 06:06 AM, Vincent Massol wrote:
>> Hi Caleb,
>>
>> On May 26, 2011, at 5:03 AM, Caleb James DeLisle wrote:
>>
>>> I would like to propose releasing 3.1-RC1 on the scheduled date. We (I)
> have lagged very badly with
>>> the milestone release dates but now is the time to get this in order.
>>> I would like to do the following:
>>>
>>> 1. Freeze on new features effective immediately. Everybody start working
> on stability.
>>
>> +1
>>
>>> 2. Any test which is observed to pass and then fail must be @Ignored and
> a bug reported for it.
>>
>> +1, we should also add a keyword so that we can easily filter them out (I
> propose "quarantined" or "flickering")
>>
>>> 3. Release happens on Monday regardless of the state of the tests.
>>
>> -1. For any failing test we must verify if the problem is a test issue or
> a real bug. If it's a real bug we need to analyze the criticity. If it's
> critical we shouldn't release without fixing it. If it's not critical then
> we can release but we'll need to add this information in the Release notes
> if it's a regression.
>
> I am happy to hold the release until you give the okay.
> I volunteer to get the storage tests running.
>
> Caleb
>
>>
>>> Since the release date is upon us, I need a quick response on this.
>>
>> Thanks
>> -Vincent