Jake's Weblog » Bugzilla

Bugzilla Install for Upcoming Events

Jake — Tue, 28 Nov 2006 23:31:41 +0000

I tried living with the trac bug system and it’s just way too limiting. Maybe if you’re the admin it’s configurable enough to live with, but as a normal user I found queries and what-not to be not very robust.

So I made a bugzilla install for my projects. Please file bugs here rather than in trac.

Road to Bugzilla 2.18 is now paved.

Jake — Sun, 16 Jan 2005 14:02:35 +0000

2 1/2 years after Bugzilla 2.16 was released, we’re very pleased to announce the release of Bugzilla 2.18. I told you we were a week ago, and now we’re there. Hop on over to bugzilla.org and check out the new version. While your there, you may also wish to read the latest status update. Of note is the fact that the 2.20 feature freeze has been lifted and that freeze will now occur in March.

Road to Bugzilla 2.18… Part III

Jake — Sun, 09 Jan 2005 10:53:45 +0000

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.

2.18 Blockers [4] [-5]
2.18 Blockers needing Review [2] [-1]
2.18 Blockers having Review, but needing Approval [0] [0]
2.18 Blockers having Review and Approval, but needing to be checked in [0] [-3]
2.18 Blocking status requested [1] [+1]

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 .

Updated Road to Bugzilla 2.18

Jake — Sat, 01 Jan 2005 09:52:03 +0000

Being that it’s now the begining of the new year, here’s an update to the numbers I posted previously: (Net change is in [Blue])

2.18 Blockers [9] [0]
2.18 Blockers needing Review [3] [-2]
2.18 Blockers having Review, but needing Approval [0] [-1]
2.18 Blockers having Review and Approval, but needing to be checked in [3] [+2]
2.18 Blocking status requested [0] [-6]

Of the two “other” bugs, bug 275408 has been marked as a duplicate of bug 245158 (which is fixed) and bug 150149 is the release notes.

A couple other bugs no longer fit into the above queries. One of those, bug 276600, is waiting on an updated patch while the other, bug 274640, is waiting on its first patch.

Overall, progress is being made. It may not be as fast as we’d all like, but it is still getting closer.

The Road to Bugzilla 2.18

Jake — Fri, 24 Dec 2004 09:22:36 +0000

We’ve been promising version 2.18 of Bugzilla for ever, it seems. I’ve only been back for a short time, but I can find emails and bug comments dating back quite a while that suggest 2.18 would be out any day. I, for one, think that it’s about time we actually made that final push. As has been suggested before, review seems to be the major hold up. Because I’ve been out for so long, I don’t feel comfortable giving review on complicated patches, but I can give review (and I’ve done it) on simple, focused patches. What’s really needed is people who are very familiar with the current Bugzilla code-base to push those final few patches to their conclusion. To help people out (to include myself), here’s some queries that give information about 2.18 blockers (number in brackets are counts as of this writing):

The 1 bug that appears to be ready for checkin was just checked into the tip, but the patch doesn’t apply to the 2.18 branch. There’s also two bugs on the blocker list that don’t fit any of the other queries. Bug 275408 is in need of a patch and bug 150149 is for the release notes. I couldn’t find a query I was happy with for these.