[Chandler-dev] Bugzilla cleanup

[Katie Capps Parlante]

The work queues are coming together, I believe now is the time to do 
some cleanup in bugzilla. We need to make some decisions about how we 
use bugzilla with the process and the new projects.

*Target Milestones*

The comments below apply to both desktop and web...

- I assume that any bug *not* in the queue should be targeted as "Future"

- I assume that we don't want to make decisions lining up bugs with 
releases in advance -- bugs get fixed in their order in the queue and we 
release on a regular schedule and/or when we've passed a major milestone 
in the queue

- Do we want one target milestone for everything in the work queue? 
Target milestones for major thresholds (like 1.0 for desktop)? Do we 
want to create a target milestone for each release and move bugs as they 
get fixed so that we have a record of what release the bug was fixed on? 
  I don't have a strong opinion on these questions yet -- interested to 
hear people's thoughts.

*Processing NEW bugs*

- I'd like to avoid the "bug councils" that we had before Preview where 
we discussed each bug in a rather large group.

- Proposal: designate one person to triage NEW bugs as they come in. The 
person would be expected to send a report to the list about the triage, 
and others could raise a flag on the list if they objected to the way a 
bug was triaged or wanted more conversation about it. The designated 
person would probably be Mimi or Sheila.

*Web Widgets, New Components*

- Proposal: use "Cosmo" bugzilla product for web widgets work (includes 
email/in-out).

- Proposal: rename "Cosmo" bugzilla product to something else

- Proposal: create a new component for each web widget

I'm open to alternatives of course, speak up if you'd like to see 
something radically different and/or if additional component cleanup 
makes sense.

Cheers,
Katie