Code imports should not have to be owned by vcs-imports
Bug #387110 reported by
Jonathan Lange
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Jonathan Lange |
Bug Description
Currently, all code imports are owned by vcs-imports. There's no technical reason for this, and it seems to make the user interface worse: not only can people not change their own import branches, but it creates an unnatural distinction between code imports and mirrored branches.
Related to bug 387106.
Related branches
lp://qastaging/~jml/launchpad/free-code-imports
- Michael Hudson-Doyle: Approve
-
Diff: 1017 lines (+432/-243)13 files modifiedlib/canonical/launchpad/security.py (+19/-3)
lib/lp/code/browser/branch.py (+4/-2)
lib/lp/code/doc/codeimport.txt (+30/-7)
lib/lp/code/mail/codeimport.py (+3/-2)
lib/lp/code/model/branch.py (+6/-2)
lib/lp/code/model/codeimport.py (+2/-4)
lib/lp/code/stories/codeimport/xx-admin-codeimport.txt (+277/-0)
lib/lp/code/stories/codeimport/xx-codeimport-machines.txt (+7/-7)
lib/lp/code/stories/codeimport/xx-create-codeimport.txt (+2/-2)
lib/lp/code/stories/codeimport/xx-edit-codeimport.txt (+42/-208)
lib/lp/code/stories/codeimport/xx-failing-codeimport.txt (+4/-3)
lib/lp/code/tests/test_branch.py (+33/-1)
lib/lp/testing/factory.py (+3/-2)
tags: | added: code-import |
Changed in launchpad-code: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: chr |
Changed in launchpad-code: | |
status: | Triaged → Fix Committed |
Changed in launchpad-code: | |
milestone: | none → 3.1.11 |
status: | Fix Committed → Fix Released |
assignee: | nobody → Jonathan Lange (jml) |
To post a comment you must log in.
And of course, once people can own their own imports, they can delete their own imports.