ec2 land: do not include already fix-committed or fix-released bugs in commit message

[Robert Collins]

I use the same branch from time to time for doing a series of work.

If you look at e.g. https://bugs.edge.launchpad.net/launchpad-foundations/+bug/632022, you'll see that it is being touched by the qa bot to make it 'qa-needstesting' after being made qa-ok.

The qa bot is doing the right thing: the landings from me have a [bug=xxx] header including that bug, *but* none of the new work on that branch referenced that bug.

If you look at the MP's for my oops branch, you can see its listing all the bugs, not just the unfixed bugs: I suspect ec2 land is picking up too many bugs, or picking up bugs that are fixed-released/fix-committed and including them inappropriately.

[Ursula Junque (ursinha)]

I've updated https://dev.launchpad.net/QAProcessContinuousRollouts adding a note that ec2 land should discard Fix Released and Fix Committed bugs. If the landing isn't explicitly set as no-qa and ec2 land finds no bugs, the command should fail.

This change is required because devels are reusing branches and ec2 land uses the bugs linked to branches, not linked to MPs (there's no such thing, I believe). Because of that tagger script is tagging a lot of already fix released bugs, retargeting milestones and lots of similar things that can make the whole QA process a mess.

[Jonathan Lange (jml)]

Presumably it only matters if they are "Fix Committed" or "Fix Released" on the 'launchpad' bug target?

[Launchpad QA Bot (lpqabot)]

Fixed in stable r12721 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12721>.