Branch edit forms don't make sense for source package branches

Bug #347751 reported by Jonathan Lange
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Jonathan Lange

Bug Description

The current branch edit forms don't make sense for package branches. They do a lot of checking to handle the case where you move a branch from one project to another, or from being a junk branch to being a project branch etc. There's also no field for selecting a source package.

All of this is symptomatic of the old world order where checking product is None was good enough to handle basically everything.

We should either make the branch edit forms provide a way of selecting a source package, and handle that appropriately, or we should just remove the ability to move a branch between products, junk and source packages. The latter might be the most expedient way for now.

Jonathan Lange (jml)
summary: - Branch edit forms don't make sense for package-branches
+ Branch edit forms don't make sense for source package branches
Jonathan Lange (jml)
Changed in launchpad-bazaar:
importance: Undecided → High
status: New → Triaged
Jonathan Lange (jml)
Changed in launchpad-bazaar:
importance: High → Medium
Jonathan Lange (jml)
Changed in launchpad-code:
assignee: nobody → Jonathan Lange (jml)
milestone: none → 2.2.5
status: Triaged → In Progress
description: updated
Revision history for this message
Jonathan Lange (jml) wrote :

The attached branch takes the more expedient option of removing the branch project / junk / package field from the edit form completely.

Jonathan Lange (jml)
Changed in launchpad-code:
status: In Progress → Fix Committed
Jonathan Lange (jml)
Changed in launchpad-code:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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