Mark's summary of how it is used is accurate.
I use a similar approach, using a separate email account to help me manage
the volume. There is definitely a bunch of ancient junk in there, which
I find happens with any successful open source project. The old stuff was
all triaged as a reasonable idea or valid bug at the time it was entered,
but over time may have become stale, irrelevant, or invalid. Sorting and/or
querying by most recently modified date helps you get a more useful picture.
I sometimes go through the old backlog and do some pruning but haven't
been able to keep up with the volume lately. We've been talking recently
about ideas for cleaning that up - any ideas you have in that are are welcome!
Mark Macdonald <mamacdon@xxxxxxxxx>
Orion developer discussions
04/23/2015 11:01 AM
how is Bugzilla used ?
I have subscribed to e-mail notifications
in every Orion bugzilla component, so I get emails for every new bug or
comment. I then archive those emails and search them for keywords when
I need to find bugs.
Admittedly this won't work for a new user,
since you won't have that email history. If there's a set of bugs that
I need to monitor closely, I create a custom bugzilla query that returns
only those bug IDs, and bookmark it.
Most Orion components have a reasonably-sized backlog which can be viewed
as a list: JS Tools, Editor, Server, Doc, Releng, Node -- these are all
OK-ish. The big problem is Client: it's a dumping ground that contains
lots of ancient junk.
Maybe we need an automated WONTFIX pass for anything with no recent activity
in (say) the last year?