Launchpad itself

Cannot change status for merge proposals that target a released series

Bug #612391 reported by Benjamin Drung
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
High
Unassigned
Ubuntu Distributed Development
New
Undecided
Unassigned

Bug Description

I can change the status for merge request that target ubuntu/<package>, but I can't change the status for merge request that target ubuntu/<series>/<package>.

Example: https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/memleak-fix/+merge/28645

James Westby (james-w)
tags: added: package-branches udd
Paul Hummer (rockstar)
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Iain Lane (laney) wrote :

This came up in a sponsorship review session at UDS, and there was just a brief discussion on IRC. It's an annoying problem for the sponsor queue after a release because there are often quite a few bugs targeted at the release which don't make it in.

We could

  - retarget all branches to either -proposed or the next release when a release is hard frozen or at initialisation of a new series
  - (idea from wgrant) create a 'development' series (but then what happens to these lp:ubuntu/release/pkg branches?)

are either of these feasible? I guess retargeting to the new dev release is the most elegant/correct solution

Revision history for this message
Robert Collins (lifeless) wrote :

I believe this occurs because you cannot upload to a released series.

I think retargeting all such uploads to $1-proposed makes a lot of sense given the rest of the modelling around releases for Ubuntu. It would be a reasonable stop-gap at least.

I think you are able to script such a thing via the API, so am going to mark this bug invalid for now; if you can't, please reopen.

Changed in launchpad:
status: Triaged → Invalid
Revision history for this message
Daniel Holbach (dholbach) wrote :

Hum... how can I retarget merge proposals of other contributors via the API? The problem AFAIUI is that 1) it's not my merge proposal, 2) it's a release which can't be uploaded to.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.