{"id":43,"date":"2004-12-24T05:22:36","date_gmt":"2004-12-24T09:22:36","guid":{"rendered":"http:\/\/www.steenhagen.us\/~jake\/trunk\/?p=43"},"modified":"2006-11-30T10:00:35","modified_gmt":"2006-11-30T15:00:35","slug":"the-road-to-bugzilla-218","status":"publish","type":"post","link":"https:\/\/jacob.steenhagen.us\/blog\/2004\/12\/the-road-to-bugzilla-218\/","title":{"rendered":"The Road to Bugzilla 2.18"},"content":{"rendered":"

We’ve been promising version 2.18 of Bugzilla for ever, it seems. I’ve only been back for a short time<\/a>, 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):<\/p>\n