Personal tools

Bugzilla:Roadmap

From MozillaWiki

Jump to: navigation, search

Contents

Bugzilla Roadmap

Introduction

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

The roadmap below is an attempt to outline what the objectives of the core Bugzilla team are for the next release. We will probably be late and we are probably too optimistic, but this gives 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).

You can also look at the old roadmap for Bugzilla 3.0 and the roadmap for Bugzilla 3.2.

Our priorities

Here is what you were waiting for: the roadmap for Bugzilla 3.4 and beyond. Tasks reported in the table are not ordered by priority as some of them may be relatively independent. The first Bugzilla version which has the corresponding features implemented is also indicated.

Task Related bugs Fully implemented on Assigned developer(s) Requirements
Bugzilla 3.4
Allow users to choose what time zone to display times in Bug 182238 August 26, 2008 LpSolit none
Implement Bug.search() for WebServices Bug 398281 January 22, 2009 mkanat none
Ability to restrict custom fields to products (like flags) Bug 371995 February 8, 2009 mkanat none
Improvements for enter_bug's UI Bug 376673 February 11, 2009 mkanat none
Bugzilla 3.6
Implement $bug->set_flags() and $attachment->set_flags() Bug 415541 August 5, 2009 LpSolit none
Bugzilla 4.0
Simplify the query.cgi UI Bug 450301 June 6, 2010 pyrzak none
Use Bug.pm to write changes and new bugs to the database Bug 122922 Bug 418342 June 18, 2010 mkanat Implement $bug->set_flag() and $attachment->set_flag()
Bug.update support in WebServices Bug 415813 July 12, 2010 mkanat, dkl Bugzilla::Bug::set_all
Bugzilla 4.2
Search.pm should not depend on the CGI Bug 398308 July 15, 2010 mkanat none
Retire old versions, components and milestones Bug 77193 August 30, 2010 dkl none
Bugzilla 4.next
Most Bugzilla modules should use Object.pm Bug 355838 Bug 297791 --- LpSolit, mkanat Use Bug.pm to write changes and new bugs to the database
Improvements to WebServices Bug 278032 --- Noura Most Bugzilla modules should use Object.pm
Bugzilla needs to deal better with branches Bug 55970 --- mkanat none
Improve Bugzilla usability Bug 490786 --- --- none
MS-SQL Support Bug 285122 --- mockodin none
Inter-Bugzilla Integration Capabilities Bug 123130
Bug 134294
--- alexeiser, dkl Use Bug.pm to write changes and new bugs to the database
Improvements to WebServices
Make Bugzilla's index.cgi (home page) useful for logged-in users Bug 130835 --- pyrzak none
Support OpenID as a an account source and login verification method Bug 294608 --- dwm none
Use tokens to authenticate email senders Bug 419203 --- LpSolit none
Refactor Bugzilla::Bugmail into real objects Bug 301447 --- manu none
Ability to specify defaults for custom fields Bug 351899 --- mkanat none