Bugzilla:Roadmap

Bugzilla Roadmap

Introduction

The trunk will soon be open again for development for 6 months, meaning that we will accept bug fixes, enhancements, new features and risky code changes. But 6 months is a short period and if we want something to be done on time when we freeze again for the release of Bugzilla 3.2, some coordination is required.

This roadmap below is an attempt to outline what the objectives of the core Bugzilla team are for 3.2. We will probably be late and we will probably be too optimistic, but this will give enough work to everyone who wants to contribute.

A very important note is that both the User Interface (UI) and the code need some cleanup, and so even if you are not familiar with Bugzilla in general or with Perl in particular, there is still enough work for you here.

So why this roadmap?

Well, to quickly summarize the main reasons, we could say:

• There is nothing more frustrating than working on a patch which will get no attention and will remain in the review queue for months, if not for years. Having clear objectives about what we want in the coming months will permit us to avoid such unfortunate situations. If we want something, we won't let it languish in the queue for months.
• Everyone is busy, but everyone wants to see things being done, and preferably as quickly as possible. Having clear objectives will make our work more efficient, as we know where the few free hours we have for writing patches will be most useful. This follows closely from the previous point, and we mention it here because we want to use our precious free time efficiently.
• Having deadlines and assigned developers will also offer a better coordination between developers. Working on some fields which conflict with someone else's work is again a waste of time, and having to unbitrot patches may take as long as writing the patch for the first time. Also, having an assigned developer per field should help in getting the work done, especially if this developer is a reviewer too. Indeed, assigned doesn't mean that he has to do the job alone, but that he is the person to contact when someone is interested in helping. He should also be able to say what work remains in the area of responsibility, and how far we are along in the process.

The Roadmap

Note

This list is subject to change at any time, depending on progress we will made and on people working on the different fields.

Latest news and summaries of Bugzilla meetings are also available. That is also the place where you can add your own suggestions to be discussed at our next meeting(s).

The old roadmap for Bugzilla 3.0 is still available.

Our priorities

This is a DRAFT only! The roadmap below has not been validated yet! Feel free to add your suggestions to the roadmap. If you don't know who would be a good "assigned developer" for a given feature, add your own name.

Look also at the complete list of bugs with [roadmap: 3.2] in their status whiteboard.

Here is what you were waiting for. Objectives described in the table are not ordered by priority as some of them may be relatively independent.

Task	Related Bugs	Estimated deadline	Assigned developer	Requirements
Supporting Oracle	Bug 189947	2007	Oracle Corp.	none
Supporting fulltext (tsearch2) on Postgresql >=8.2	Bug 365258	2007	bkor	none
Adding AJAX for some features	Bug 325501	2007	?	none
Customizing statuses and workflow	Bug 101179	2007	?	none
Centralizing bug editing in Bug.pm	Bug 122922 Bug 367914	2007	mkanat	none
Inter-Bugzilla Integration Capabilities	Bug 123130 Bug 128613 Bug 127871 Bug 127875	2007	valor	none
Bugmail available in different formats (HTML, XML, plain text)	Bug 65477 Bug 235720	2007	?	none
Support for small devices	Bug 101865	2007	?	none
Support for DB transactions	Bug 121069	2007	mkanat	none
Improve request.cgi	Bug 184252	2007	LpSolit	none
UI for checksetup.pl	Bug 270066	2007	mkanat	none
Improvements to the charting and report systems	Bug 271673	2007	LpSolit	none
New types for custom fields	Bug 91037	2007	mkanat	none
Remove intermediate pages in admin sections	Bug 325487	2007	LpSolit	none
Improve usability for common tasks	Bug 344619	2007	?	none
Most Bugzilla modules should use Object.pm	Bug 355838 Bug 297791	2007	?	none
Clean up old ugly code	Bug 271023	2007	LpSolit, bkor	Centralizing bug editing in Bug.pm

Ja