What do we do about 2.18?

[David Miller]

In theory, we did a feature freeze on March 15th in preparation for the 
2.18 release.  A few things have slipped in here and there, but they've 
mostly been minor low-risk stuff.  However, we still have 11 bugs left 
in the buglist that are pretty much blocker quality, and have sat there 
for a while.

Meanwhile, there's several projects people have shown interest in 
landing soon, and have held off on putting major effort into them 
because they can't go in until after we branch for 2.18.

Typically at this point in the release cycle, we don't branch until the 
first Release Candidate (RC) goes out (in an effort to get people to 
spend their labor on the release blockers).

March 15th was 2 1/2 months ago.  The freeze was only intended to last a 
month before RC.  And here we still sit.

I still intend to stick to the schedule for 2.20.  It may happen a month 
after 2.18 does at this rate. :)  Because of the number of big things 
waiting for us to branch, I'm confident 2.20 will be worth the version 
number bump, despite the short time frame.  Because of the short time 
frame, I'm not so worried about it taking forever to push out the door 
like 2.18 is.

So, that leaves us with a decision now.  We either get as many folks to 
help as possible to kill off the last blockers, or we branch now and 
forget about waiting for an RC before we branch.  Personally I'd really 
like to see 2.18 out sooner than later, which makes me want to continue 
to hold the branch hostage...

Here's what's left:

checksetup.pl fails to remove product index from milestones table in 
upgrade from 2.14.x
=> http://bugzilla.mozilla.org/show_bug.cgi?id=244756
Status: UNCONFIRMED - Needs someone to attempt to reproduce or find the 
code that's doing the wrong thing.  If it can be reproduced or visually 
pointed out in the code, this is a release blocker.

"View All" attachment statuses field empty
=> http://bugzilla.mozilla.org/show_bug.cgi?id=223541
Status: This is a small UI tweak, polish issue.  Should be really easy 
if someone wants to tackle it.  Data in question should be available to 
the template already, the template just needs to reference it properly.

Flag system dies when changing a deleted flag
=> http://bugzilla.mozilla.org/show_bug.cgi?id=223878
Status: Needs a patch.  Problem seems to have been identified in the bug 
comments, but no one has written a patch to fix it yet.  Best fix is 
probably to find some way to make flag IDs unique so they never get 
reused (auto_increment?), and add the flag type to a hidden field in the 
form so it knows what to do if it encounters one that's been deleted.

Add group controls to new charts
=> http://bugzilla.mozilla.org/show_bug.cgi?id=225687
This is kind of a security hole, but the bug is public because the 
problem has been publicly disclosed since the feature was introduced. 
The new chart system changes the way series are defined in the charts so 
that they're no longer explicitly tied to products.  However, it 
migrates the old data and uses the product names for the series when it 
creates them.  This means hidden products would have their names visible 
(but no actual bug data) unless the admin when back and deleted them 
from the new charts.  Current status: lots of discussion about the best 
way to fix it. (see other threads on this list recently).  The leading 
theory at the moment is to go ahead and make the new system (optionally) 
explicitly tie a series to a product, and make that tie on each of the 
datasets that are migrated from the old system.  This is probably Gerv's 
baby, but the patch is going to be substantial and he'll need review 
help when it's done.  We can't release 2.18 with this hole here though.

Boolean charts are broken on reporting pages
=> http://bugzilla.mozilla.org/show_bug.cgi?id=179671
Status: has patch, waiting for review

That's 5 bugs.  We're close :)

I'm going on vacation this coming week, and will probably be completely 
offline from later this morning until Sunday the 6th.  It'd make my day 
if I came back to things being ready to go :)  As always, you can still 
get approvals from Myk while I'm gone.

-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/