What lies ahead
justdave at syndicomm.com
Wed Apr 23 06:35:34 UTC 2003
Bugzilla 2.17.4 will be posted within the next 24 hours.
It's time to start reviewing our goals for 2.18 and deciding what's
important for us to keep on the list and what we might want to push off.
As far as timing goes, I'm not going to set a date, we've been bit by that
too many times in the past. The answer to "when is 2.18 coming out?" will
continue to be "When it's done." However, we probably do need to do it
sooner rather than later, so reducing our list of goals is probably a good
idea at this point. If we can pare this down appropriately, I'm thinking
along the lines of 2.17.5 being the last developer release prior to 2.18
release candidates. That may or may not be realistic, but we'll see.
A quick query of bzbot in IRC tells me that we have 1096 bugs currently
targeted at 2.18, with 478 of those fixed so far, leaving 618 still to be
For comparison, we fixed 550 bugs for version 2.16.
The current "2.18 goals" taken from http://www.bugzilla.org/roadmap.html
(with completed items removed, and comments by me added):
* Integrate inbound email into the mainline Bugzilla code (currently
it's in contrib and very messy, if it even still works). (94850)
Matt Barnson says he's currently working on this, so it might get done
before then after all. :)
* HTML 4.01 Transitional compliance for all administrative pages.
* Templatization of all administrative pages.
* Enable Perl's taint mode for all administrative pages.
These three are pretty much lumped together as a complete rewrite of the
administration pages (because they need it badly).
Templatization and rewrite of the admin pages, while a lofty goal, and
something we really should do, seems to be going really slow. I'd really
like to see this stay on the list, but we're going to have to push somebody
into doing it I think. :)
* Customizable statuses and resolutions.
This doesn't seem to be going anywhere lately, I'm leaning towards pushing
this one off.
* Compatibility with Postgres SQL. (98304)
Though not listed here, it's quite possible that Sybase support will
actually make it (although it may be checked in partially incomplete and
labelled as unsupported, due to some quirks in Sybase that sites are just
going to have to live with if they decide they really want to use Sybase
with Bugzilla - I did the Sybase conversion, and I personally would not
recommend it, because Sybase sucks for web-based apps, but hey, they paid
me for it :)
I have no clue of the current status of Postgres support. It was pretty
close to landing at one point, but it's quite bitrotted now, and I haven't
seen anything done with it lately. Sybase may end up landing first,
* Out-of-the-box compatibility with Win32.
Personally, I'd like to see this stay on the list. As much as we all hate
it, there's a lot of PHBs out there that won't let people do anything if
you can't do it on Windows... and we're so close now anyway...
* An optional way to pick users from a list for the assignee and
QAContact fields. (52557 and/or 102942)
I've seen a lot of activity on this front lately. I think it'll make it.
* Continue to catch up with contributed patches from the backlog
generated when we had the tree locked down during the 2.14 development
I think we may be at a point where we can drop this from the list. There's
a lot of stuff queued for review out there now with the new review system.
:) Nowhere near as much stuff left in the queue as there was when we
finished the user-facing templatization. And the entire architecture of
Bugzilla has been changing so fast lately.
Comments from the peanut gallery? :)
Dave Miller Project Leader, Bugzilla Bug Tracking System
More information about the developers