Road to Bugzilla 2.18… Part III

A little more than a week has passed since I last updated my “Road to Bugzilla 2.18” numbers. Once again, Blue numbers will represent the net change since last time.

Reviewing my “Other” bugs from last time, we see that bug 150149 (the release notes) has now moved from the “Other” category to the “Review Requested” one. Bug 276600 and bug 274640 are now both FIXED.

New into the “Other” category, we have bug 276237, which deals with a charting issue (a mysterious problem that may be specific to bmo), and bug 159790, which is simply the release tracking bug (which should have been a blocker all along).

So, what does all this mean? I’d say it means we’re really close now. In fact, it looks like 2.18 may actually be out before I leave Iraq ;).

One thought on “Road to Bugzilla 2.18… Part III”

  1. This assumes that the Bugzilla team decides to stay on the current release schedule. As a user who’s just about to deploy an installation, it’s rather disheartening to have the Bugzilla developers on the mailing list talk about dropping 2.18 when its so close to release and jumping ahead to 2.20 for about one new feature.

Leave a Reply