Re: Triage Plan for Firefox Components
Emma Humphries <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.seamonkey |
|---|---|
| Message-ID | <CAL_vYcpBkOtKmMDn_CG-Dizd+LEBuLwF-aTsRX2tYr0EP3dCSw@mail.gmail.com> |
You're using a field intended for describing features to be a bug summary, which it's not. And this is part of what's driving this work. We have a couple of hundred components making up Firefox in Bugzilla and multiple teams all using Bugzilla in slightly different ways, so that it becomes increasingly difficult to understand what's going on without non-trivial insider knowledge. -- Emma On Thu, Apr 7, 2016 at 6:41 AM, Philip Chee <[email protected]> wrote: > On 07/04/2016 14:50, L. David Baron wrote: > > > (I'd much rather a bug report be editable text, with history > > available, for answers to these or similar questions -- rather than > > a stream of permanent comments. But we seem stuck with the horrid > > stream-of-comments Bugzilla format, which means I try to ignore the > > comments as much as I can. Then again, a 200 character summary is > > often good enough to answer the above 5 questions. As with the rest > > of the Internet, don't read the comments.) > > I'm currently using the "User Story" text area to provide an up to date > summary of the state of the bug. This works great since it's editable. > > Phil > > -- > Philip Chee <[email protected]>, <[email protected]> > http://flashblock.mozdev.org/ http://xsidebar.mozdev.org > Guard us from the she-wolf and the wolf, and guard us from the thief, > oh Night, and so be good for us to pass. > _______________________________________________ > dev-planning mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-planning >