On 09/23/2012 12:54 PM, Krinkle wrote:
I think master is more stable then whatever wmf branch. I know because of commits recently merged and whatnot.
This feels like a strange statement to me. I'm willing to believe that bugs found in the WMF branch have been fixed on master, but it seems obvious that new bugs would also have been introduced.
Still, the pre-merge review + rapid release cycle would probably make master more stable than it was for other releases.
If there are problems we'll find them in the release candidate period. And by that time we'll have had a new wmf branch as well to see how the latest code performs on wmf.
Good point.
Also, this bugzilla query should be empty before release as well (either by fixing bugs, or reviewing/merging pending commits that claim to fix stuff, or deferring the bug to a later release etc.). People assign and block things usually for a reason:
Link shortened: http://hexm.de/lp
This is a very good point.
I think the thing to do is to make a new RC from master (as you suggest) and organize a triage of 1.20 bugs.
I'll also put a comment on all those bugs inviting people to participate in the triage so that we have a way to gauge interest and have people test them against the beta cluster (or a 1.20 installation on labs).
I can hold a triage for blockers at UTC1100 on Tue, October 2 (http://hexm.de/lr). At this point, there are over 100 non-enhancment bugs marked for 1.20. Please help trim the list before then.
Mark.