Bugzilla:Roadmap: Difference between revisions
m (The trunk is now OPEN for development. Checkins still require the approval flag to be set by justdave or myk, but will generally be approved for anything that isn't controversial. :) Have fun!) |
m (The trunk is now OPEN for development. Checkins still require the approval flag to be set by justdave or myk, but will generally be approved for anything that isn't controversial. :) Have fun!) |
||
| Line 1: | Line 1: | ||
== Bugzilla Roadmap == | == Bugzilla Roadmap == | ||
=== Introduction === | === Introduction === | ||
The trunk is now open for development again | The trunk is now open for development again, and for the next 6 months, we will again 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 on Sept 15, 2006 for the release of Bugzilla 2.24 (maybe 3.0?), some coordination is required. | ||
This roadmap below is an attempt to outline what the objectives of the core Bugzilla team are for 3.0. If we make this list (or major portions of it) by September, we'll be happy to call it 3.0 instead of 2.24. We will probably be late and we will probably be too optimistic, but this will give enough work to everyone who wants to contribute. | This roadmap below is an attempt to outline what the objectives of the core Bugzilla team are for 3.0. If we make this list (or major portions of it) by September, we'll be happy to call it 3.0 instead of 2.24. We will probably be late and we will probably be too optimistic, but this will give enough work to everyone who wants to contribute. | ||
Revision as of 11:00, 31 May 2006
Bugzilla Roadmap
Introduction
The trunk is now open for development again, and for the next 6 months, we will again 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 on Sept 15, 2006 for the release of Bugzilla 2.24 (maybe 3.0?), some coordination is required.
This roadmap below is an attempt to outline what the objectives of the core Bugzilla team are for 3.0. If we make this list (or major portions of it) by September, we'll be happy to call it 3.0 instead of 2.24. 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).
Our priorities
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 |
|---|---|---|---|---|
| Removing versioncache | Bug 110503 | April, 2006 | mkanat | none |
| Removing globals.pl | Bug 87411 | June, 2006 | mkanat, LpSolit | Removing versioncache |
| Removing deprecated SQL routines (SendSQL, SqlQuote, ...) | Bug 278017 | June, 2006 | wicked, LpSolit | Removing globals.pl |
| Rewriting Flag.pm and FlagType.pm (and probably merging them) | Bug 304699 | June, 2006 | LpSolit | none |
| Centralizing bug creation and editing in Bug.pm | Bug 122922 | July, 2006 | mkanat, LpSolit | Removing globals.pl, Removing versioncache |
| Supporting Oracle | Bug 189947 | July, 2006 | Oracle Corp | none |
| Support for mod_perl | Bug 87406 | August, 2006 | mkanat | Removing globals.pl |
| Implementing custom fields | Bug 91037 | August, 2006 | myk | none |
| Adding AJAX for some features | Bug 325501 | August, 2006 (?) | gandalf | none |
| Supporting multiple skins | Bug 321556 | August, 2006 | wurblzap | none |
| Having a better UI | (no meta bug) | August, 2006 | myk, gandalf | Supporting multiple skins, Adding AJAX for some features, Implementing custom fields |
| Customizing resolutions | Bug 94534 | September, 2006 | LpSolit | none |
| Customizing statuses and workflow | Bug 101179 | September, 2006 | karl | Customised resolutions(?) |
| Implementing web services | Bug 224577 | September, 2006(?) | ? | Centralizing bug creation and editing in Bug.pm |
| Implementing inbound mail | Bug 94850 | September, 2006(?) | Colin | Centralizing bug creation and editing in Bug.pm |