Merge lp:~jml/launchpad/p3a-commercial-subscription into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Curtis Hovey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 15403 |
Proposed branch: | lp:~jml/launchpad/p3a-commercial-subscription |
Merge into: | lp:launchpad |
Prerequisite: | lp:~jml/launchpad/p3a-private-team |
Diff against target: |
195 lines (+59/-30) 5 files modified
lib/lp/registry/browser/tests/test_team.py (+2/-4) lib/lp/soyuz/model/archive.py (+8/-11) lib/lp/soyuz/tests/test_archive.py (+8/-1) lib/lp/soyuz/tests/test_archive_privacy.py (+35/-14) lib/lp/testing/factory.py (+6/-0) |
To merge this branch: | bzr merge lp:~jml/launchpad/p3a-commercial-subscription |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Curtis Hovey (community) | code | Approve | |
Review via email: mp+109602@code.launchpad.net |
Commit message
Allow people with commercial subscriptions to create private PPAs via the API.
Description of the change
We want to be able to create private PPAs without having commercial admin privileges. After an implementation discussion with sinzui (summarized https:/
What it does *not* do is allow people with commercial subscription to change privacy of existing PPAs. This is because I can't figure out how to separate the 'private' attribute from the rest of the attributes requiring 'launchpad.
Also, this branch does not update the web UI.
Thank you. I think this is fine to land.