Setting specification policy to "proprietary" does not add "proprietary" to sharing table
Bug #1061621 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Aaron Bentley | ||
Bug Description
Setting the specification sharing policy to "proprietary" does not enable sharing "proprietary" information, but it does with bugs. To demonstrate:
1. create a new project with the Apache license (because Other/Proprietary defaults bugs & branches to proprietary)
2. change the project license to other/proprietary
3. go to +sharing. "Proprietary" will not be listed under "Who it's shared with".
4. Change specification sharing policy to proprietary. "Proprietary" will not be listed under "Who it's shared with".
5. Reload. "Proprietary" will not be listed under "Who it's shared with".
6. Change bug sharing policy to proprietary. "Proprietary" *will* be listed under "Who it's shared with".
Related branches
lp:~abentley/launchpad/specification-policy
- Richard Harding (community): Approve
-
Diff: 176 lines (+45/-16)7 files modifiedlib/lp/blueprints/browser/tests/test_specification.py (+0/-4)
lib/lp/blueprints/model/specification.py (+1/-0)
lib/lp/registry/model/product.py (+7/-2)
lib/lp/registry/services/tests/test_sharingservice.py (+4/-5)
lib/lp/registry/tests/test_product.py (+25/-1)
lib/lp/registry/tests/test_sharingjob.py (+0/-2)
lib/lp/testing/factory.py (+8/-2)
| tags: | added: disclosure |
| tags: |
added: information-type sharing removed: disclosure |
| Changed in launchpad: | |
| assignee: | nobody → Aaron Bentley (abentley) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r16127 <http://