Proposed changes to workflow bug management

[Ben Collins]

On Tue, 2008-05-27 at 12:33 +0200, Reinhard Tartler wrote:
> CC'ing the bugsquad for more input on this idea.
> 
> Henrik Nilsen Omma <henrik at ubuntu.com> writes:
> 
> > Reinhard Tartler wrote:
> >> I think we should ask the launchpad guys to prevent bugs to be
> >> assigned to a team. I know the kernel team is doing this, but I still
> >> haven't found out why. Could some member of the kernel team give a
> >> rationale for this please?
> >>   
> > This is no longer current practice in the kernel team and the bugs 
> > currently assigned to the team will be un-assigned. Bugs are now 
> > assigned to individuals directly.
> 
> So is my idea a basis on which consesus is reachable? If yes, I'm going
> to file a malone bug on malone for preventing teams to be assigned to a
> bug in ubuntu.

I still think it's useful to have this feature. I don't see why
assigning a bug to a team as part of workflow is so difficult to
understand as a concept.

Take the intrepid linux-ports package that will be coming down the pipe.
The bugs will be split up on the basis of architecture. So assigning
bugs to the ubuntu-{powerpc,ia64,hppa,sparc} teams as a triage step
makes sense, and immediately shows responsibility. Then individuals in
those teams can take the bug.

No one has yet explained a better way to handle this sort of workflow,
and until they do, I personally veto removing the ability to assign bugs
to a team.