26 May
2011
26 May
'11
12:06 p.m.
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.
Since the release date is upon us, I need a quick
response on this.
Thanks
-Vincent