branchupgradejob should not upgrade in place

Bug #385032 reported by Michael Hudson-Doyle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Paul Hummer

Bug Description

Instead, it should copy the branch to one side, upgrade there, pull any new revisions in and then replace the old branch with the upgraded one.

Tags: lp-code
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

The Launchpad branch format change ate the end of my 2.2.6 cycle.

Changed in launchpad-code:
milestone: 2.2.6 → 2.2.7
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Not going to make 2.2.7 :(

Changed in launchpad-code:
milestone: 2.2.7 → none
Changed in launchpad-code:
milestone: none → 2.2.9
Changed in launchpad-code:
milestone: 2.2.9 → 2.2.8
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Not going to make 2.2.8.

Changed in launchpad-code:
milestone: 2.2.8 → 3.0
Tim Penhey (thumper)
Changed in launchpad-code:
milestone: 3.0 → 3.1.10
Tim Penhey (thumper)
Changed in launchpad-code:
assignee: Michael Hudson (mwhudson) → Paul Hummer (rockstar)
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Moved to 3.1.11 so I can close 3.1.10 milestone

Changed in launchpad-code:
milestone: 3.1.10 → 3.1.11
Paul Hummer (rockstar)
Changed in launchpad-code:
status: Triaged → Fix Released
milestone: 3.1.11 → 3.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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