Users should be able to make private branches of public projects
Bug #527900 reported by
Ted Gould
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Ian Booth |
Bug Description
For various tasks we'd like to have a private branch of an otherwise public project. It would seem that this should be a user or by group setting. I think that it should work similar to +junk. So if I needed a private branch I could do:
bzr branch lp:linux
<fix security embargoed feature>
bzr push lp:~linux-security-team/+private/linux/cve1234
This would keep the workflow clean, but allow for making private branches that could be seen by a team.
Thanks!
Related branches
lp:~wallyworld/launchpad/make-private-branches-527900
- Curtis Hovey (community): Approve (code)
-
Diff: 589 lines (+308/-40)10 files modifiedlib/lp/bugs/interfaces/bugtask.py (+9/-1)
lib/lp/bugs/model/bugtasksearch.py (+4/-0)
lib/lp/bugs/tests/test_bugtask_search.py (+15/-0)
lib/lp/code/browser/branch.py (+52/-29)
lib/lp/code/browser/tests/test_branch.py (+44/-3)
lib/lp/code/interfaces/branch.py (+19/-0)
lib/lp/code/model/branch.py (+27/-0)
lib/lp/code/model/tests/test_branch.py (+100/-1)
lib/lp/registry/tests/test_information_type_vocabulary.py (+22/-4)
lib/lp/registry/vocabularies.py (+16/-2)
Changed in launchpad: | |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
tags: | added: feature |
tags: | added: information-type |
Changed in launchpad: | |
importance: | Low → High |
status: | Triaged → In Progress |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in launchpad: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
User can have private branches for public projects, they need to ask so that the reason are understood.