[equinox-dev] bug triage process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[equinox-dev] bug triage process

From: Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
Date: Wed, 15 Oct 2008 11:34:37 -0700
Delivered-to: equinox-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/equinox-dev>
List-help: <mailto:equinox-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=unsubscribe>

In the p2 call this week (http://wiki.eclipse.org/Equinox/p2/Meetings/20081014#Minutes)
we talked about bug triage and trying to assign real owners to bugs. We also mentioned assigning them directly within the team when we open a bug, to avoid a bunch of bug noise.

Just now I opened a bug, assigned it directly to Pascal. But then I remembered...it's important that when you first open a bug, you should leave the owner as the inbox. Otherwise people watching the inbox to keep up with what's going on won't see the bug go by.

Just wanted to bring up this point.

susan

Prev by Date: Re: [equinox-dev] Component Resolve Thread and the context classloader
Next by Date: Re: [equinox-dev] p2 publisher tests?
Previous by thread: [equinox-dev] Component Resolve Thread and the context classloader
Next by thread: [equinox-dev] BSF, Groovy, class/OSGi resolution
Index(es):
- Date
- Thread

Breadcrumbs