Max Kanat-Alexander Reporter
	Description • 19 years ago

This bug represents, in Bugzilla, the tasks outlined at http://wiki.mozilla.org/Bugzilla:Roadmap. It's here so that we can see in a single dependency tree, overall, how we're doing on our progress toward Bugzilla 3.0.

No dependencies should be added to this bug other than those listed in the Roadmap.

Note that the critical bugs which must be resolved before Bugzilla can be considered 3.0 are:

bug 87406
bug 91037
bug 321556

	Bernhard Merkle
	Comment 1 • 19 years ago

what is the status about bug 91037 ?
will it be in 2.24 ?
is there a patch for 2.22 ?

	Frédéric Buclin
	Comment 2 • 19 years ago

Now that nobody is working on Oracle support anymore, I think it's reasonable to remove it from our roadmap (the roadmap on wiki has already been updated). This doesn't mean we won't take it for 3.0 if we are ready on time.

	Max Kanat-Alexander Reporter
	Comment 3 • 18 years ago

Looks like Firefox did some strange selecting of the group radio boxes on the mass-change page when I clicked refresh in my browser before that last mass-change. This is not really a security bug. :-)

	Frédéric Buclin
	Comment 4 • 18 years ago

Please do not block this bug with features which have not been discussed and approved during our initial meeting.

	Max Kanat-Alexander Reporter
	Comment 5 • 18 years ago

bug 101179 isn't on the roadmap for 3.0 anymore. Nor is bug 325501.

	Frédéric Buclin
	Comment 6 • 18 years ago

All tasks on our roadmap for 3.0 have been fixed, see http://wiki.mozilla.org/Bugzilla:Roadmap

	Kevin Benton
	Comment 7 • 18 years ago

I'm confused - the dependency tree doesn't agree.  In fact, if I click on show dependency tree, it only shows this bug as being resolved.  One of the apparently resolved bugs is 87406, however, it doesn't show up in the dependency tree.  Is that my misunderstanding of how the dependency tree should work or is that a bug?

	Frédéric Buclin
	Comment 8 • 18 years ago

Only open bugs are displayed in the tree by default, explaining why this bug is the only one being marked as fixed at first sight. Then the remaining blockers of this bug involve more new features than the strict set of features we wanted for 3.0.