We need a graveyard product




17 years ago
8 years ago


(Reporter: timeless, Assigned: ian)


Firefox Tracking Flags

(Not tracked)




17 years ago
The product does not need a QA or an Assignee (use "" if possible).
I'd suggest that we create one component for each other b.m.o product.
Ideally the product would not allow people to file bugs into it.
As components are deleted from other products, their bugs would be moved into 
the appropriate component in this product.

... Perhaps bugzilla itself should sport this functionality: ie the bugzilla 
admin says: I want to delete this non empty component (perhaps bugzilla will 
offer an additional comments field so the admin can explain why the component 
was deleted).
A. makes sure that a graveyard exists,
B. that a component for the product from which it's deleting exists, 
C (optional). files a bug into the graveyard indicating the component that was 
deleted, its description, qa contact, and bug stats.
D. moves all bugs in the selected component into graveyard: old product
E. deletes old the component.
For the time being, we'll do this manually.
The sequence for us will be [asa: AB this bug - once] anyone*: C, me: D, asa: 
[Obviously people would have to agree (with 'anyone') that it's time to delete 
the component at step C before I move the bugs to the graveyard ...]

Why we want a graveyard product/component.  Right now people can't delete bugs, 
and you can't delete a component until it has no bugs. Many people don't like 
the idea of actually deleting bugs (and the database doesn't either).

I think the first candidates for this graveyard would be PICS, Dom Viewer, and 
some XPCOM miscellaneous component.
I agree that this would be nice to help shake out now-useless things like
MozClassic and clear up our component selection.
I personally don't think this is a good idea at all.  The correct fix for this
is bug 77193 in my opinion.  Myk already used this trick on groups, it should be
possible to do something similar with components without too much trouble.
OS: Windows 2000 → All
Hardware: PC → All

Comment 3

17 years ago
Dave, is 77193 likely to happen any time soon?

Comment 4

17 years ago
one reason i like the idea of moving things out of a product is that in my SQL 
ignorant view of the world it'd make searching for live bugs in the product 
faster. i'd imagine that the bug you referenced wouldn't do that, or would 
incur an extra cost (some other join/condition).
I'll defer to Myk on the timetable for that other bug since he's the most-likely
person to implement it.  Unless he says otherwise though, I'd say "soon" is
likely not the answer, since most of the other interested folks don't have much
time to code lately.  If mozilla.org needs something quick, the product might be
the way to go.
I have a pretty full plate at the moment; I won't have time to look at 77193 in
the near future unless I do it in lieu of other important work.

Comment 7

17 years ago
Assignee: asa → ian

Comment 8

17 years ago
WONTFIX. We'll just wait for Bugzilla to support this natively; in the meantime
Bugzilla-General is fine.
Last Resolved: 17 years ago
Resolution: --- → WONTFIX

Comment 9

17 years ago
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.