On Feb 22, 2008, at 4:35 PM, Katie Capps Parlante wrote:
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"
This makes sense.
- 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.
If we are just dealing with timed releases, I don't think it makes
sense to move bugs over to a target milestone as they get fixed. It's
just one more thing to do and it adds more targets to the list which
could just confuse people. We should keep it simple and just assign
the whole queue to some major milestone. It's easy to see what is in
the queue and what is not (future). I am assuming you can get a
checkin report that lists out what bugs were fixed so we can put that
out with the release notes. I guess I don't see any advantage to
having this in bugzilla. That's my 2 cents.
*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.
Sure I can do this. I will consult with others on an as needed basis
since in many cases I might need some developer and/or design input.
*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 don't have a strong opinion on this. When I created all the web UI
bugs I assigned them to "Calendar UI" since there wasn't an
appropriate component. Since we are changing the components, we should
probably rename this one or create a new one since it's not just a
calendar UI anymore. I think I just assigned the web widgets to
General but I will go back and reassign everything to whatever we
decide.
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
