Lack of release targeting in Malone (was Re: Bugging questions)

[Matthew East]

On Tue, 2006-05-02 at 11:43 -0700, Matt Zimmerman wrote:
> On Tue, May 02, 2006 at 07:29:09PM +0100, Matthew East wrote:
> > Seems that us normal users can't change or even see this. So the use of
> > milestones on bugs is not really useful, because the bug reporter can't
> > tell what milestone has been set for his bug (at least through the UI,
> > he can do it through email), and the bug triager can't change it unless
> > he is in ubuntu-drivers (and very few triagers of (say) ubuntu-docs bugs
> > are).
> 
> This is why Malone makes a distinction between distribution packages and
> upstream products.  You should target your fixes to releases of ubuntu-docs,
> and Ubuntu drivers should target Ubuntu releases.  If you feel that a bug
> should be fixed for Dapper, notify me and I will take that decision.

The distinction is a tricky one for us, because everyone files bugs in
ubuntu-docs, and often they are packaging bugs, which we will fix, and
Daniel will upload. But, I suppose that to be consistent with Malone we
really have to continually reassign bugs to the upstream product
releases, even though we don't release ubuntu-docs anywhere except for
Ubuntu.

So, that handles the "changing" part. Not the "seeing" bit though. There
is literally no field which tells the normal user what release has been
targetted, AFAICS.

> My understanding is that in the future, Malone will incorporate this
> workflow: anyone can "nominate" a bug for a milestone, but an authority must
> confirm it.

Sounds quite cool, if the authorities have time to deal with all the requests.

Matt
-- 
mdke at ubuntu.com
gnupg pub 1024D/0E6B06FF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/launchpad-users/attachments/20060502/ecdef094/attachment.pgp