[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] Triaged bugs
- From: Nitin Dahyabhai <nitind@xxxxxxxxxx>
- Date: Thu, 7 Jul 2005 11:05:35 -0400
- Delivered-to: email@example.com
- User-agent: Mutt/1.4.1i
On Thu, Jul 07, 2005 at 10:19:33AM -0400, John Lanuti wrote:
> Placing a developer or component lead's name on the defect gives the
> reporter a sense of accountability. If I have a question about the
> defect or when it will be ready, I know who to email, who to ask.
The right place for those kinds of questions is in the bug itself, out
in the open. This is especially important if the bug ends up being
reassigned to someone else--the paper trail already exists for them to
> ...j2ee tools has like 10 components, most of which are shared with
> other development teams. Having to constantly triage all 10
> components is very tedious. If all the defects are still under the
> root component, then we would have to read all that components defects
> every time just to see if any of them fall under our responsibility.
> And then this has to repeated for all 10 components.
Watching the component-inbox user in your email preferences delivers
opened bugs right to your bugzilla email address. I suggest reading and
triaging them as they come in since that removes the need to scan the
entire list of components repeatedly. This is especially useful if you
need to be aware of bugs in the prereqs or the wst.common component (for
example). The number of incoming bugs is the number of incoming bugs,
regardless of the number of components.