[RFD] Milestone usage (Re: [Bug 422849] Re: Incorrect conversions in 2.0rc1 and bzr.dev)

Martin Pool mbp at canonical.com
Mon Sep 7 03:12:36 BST 2009


2009/9/7 Robert Collins <robertc at robertcollins.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Pool wrote:
>
>> * target blockers to the next release, even if that's an rc
>> * if someone wants to observe changes in a stable series, they should
>> follow that series, eg
>> <https://bugs.staging.launchpad.net/bzr/2.0/+bugs>
>
> So one thing that concerns me about that, is that in launchpad bugs in a
> series represent 'existence', not 'to be fixed in'. Or at least it used
> to. I think we should be seek clarification about what launchpad's
> developers *think* it means, and will continue to mean.
>
> That means that the 2.0/+bugs list could get very big and not be helpful
> to people wanting to track the series.

That's not what I understand it to mean -- though I don't mind checking.

My evidence for this, beyond a general impression, is

1- they're called BugTasks, ie the task of fixing the bug
2- launchpad has a specific feature concept "infestation" for tracking
"present in a series" and it's not done yet
3- the control to create one of these is (mis)labelled "target to
release" (should say "series"), not "mark present in"
4- if unprivileged malone users use that control, it creates a
"nominate for fix in" which can then be accepted or declined by the
developers

-- 
Martin <http://launchpad.net/~mbp/>



More information about the bazaar mailing list