← Back to team overview

ubuntu-phone team mailing list archive

Re: New Landing Plan format!

 

On Tue, Dec 17, 2013 at 10:30 PM, Martin Pitt <martin.pitt@xxxxxxxxxx> wrote:
> What a nice christmas present! I already had feared we'd be stuck with
> this <argh> spreadsheet for much longer, so thanks for getting rid of
> it! No more IRC hunting "can someone pretty please add this".

I'm glad somebody liked it ;-)

>> When you want to request a new release of your project, you file a
>> bug[0] against landing-plan. Please include the name of the launchpad
>> project you want released, and a short blurb about why (what bug it
>> fixes, or what feature it implements).
>
> If it fixes a bug, would it be acceptable/helpful to add a
> landing-plan task to the existing bug, so that all information is in
> one place? If it's a bug-less new feature or it fixes several bugs, a
> new landing-plan bug report is of course better.

Well, I have mixed feelings about this. I certainly appreciate the
ease of simply adding a landing-plan task to an existing bug, and the
idea appeals to me for simplicity sake, but my concern is that
everybody will just start adding landing-plan tasks to *every* bug,
and that is just even more pointless busywork on top of the pointless
busywork that we already have.

The point of the landing-plan bugs is that they're a sort of meta-bug,
they're meant to say "ok, we are announcing our intent to stage a
release that fixes bugs A, B, C, D. The first three are in trunk
already, bug D has a merge proposal that will land soon, please
coordinate the merging of that branch and the releasing of the
package" So because of that it doesn't make a lot of sense to share a
bug number with any one specific bug. Each landing plan bug should
simply link to the bugs & merges that it intends to include in it's
release.

My goal is to see less than one landing-plan bug per each "regular"
bug that we have, ie, that you only file one landing-plan bug per
project per week, not that a landing-plan task gets added to every
little bug that gets fixed.


References