Merge lp:~abentley/launchpad/fix-blueprints-home-with-proprietary into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Aaron Bentley on 2012-09-14 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 15961 |
| Proposed branch: | lp:~abentley/launchpad/fix-blueprints-home-with-proprietary |
| Merge into: | lp:launchpad |
| Diff against target: |
50 lines (+25/-1) 2 files modified
lib/lp/blueprints/browser/tests/test_specification.py (+23/-0) lib/lp/blueprints/model/specification.py (+2/-1) |
| To merge this branch: | bzr merge lp:~abentley/launchpad/fix-blueprints-home-with-proprietary |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Deryck Hodge (community) | 2012-09-14 | Approve on 2012-09-14 | |
|
Review via email:
|
|||
Commit Message
Blueprints home page tolerates proprietary Specifications.
Description of the Change
= Summary =
Fix bug #1050960: embargoed (or proprietary) specifications break the blueprints front page
== Proposed fix ==
Show only PUBLIC specifications on the blueprints home page
== Pre-implementation notes ==
Discussed with deryck.
== LOC Rationale ==
Part of Private Projects
== Implementation details ==
This was the simplest-possible fix for this critical bug, that would otherwise block us from deploying Blueprints.
== Tests ==
bin/test -t test_index_with_pro spec
== Demo and Q/A ==
View the Blueprints home page. You should not get a "Not allowed" page. Create a Proprietary blueprint. View the Blueprints home page. You should not get a "Not allowed" page, but the blueprint you created will not be listed under "Recently registered".
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
