private projects can create a release
Bug #1086002 reported by
Richard Harding
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
j.c.sackett |
Bug Description
Releases are a leak point for private products and needs to be blocked.
Related branches
lp:~jcsackett/launchpad/no-private-releases
- Benji York (community): Approve (code)
-
Diff: 265 lines (+109/-2)6 files modifiedlib/lp/registry/browser/productrelease.py (+19/-0)
lib/lp/registry/browser/tests/test_productrelease.py (+56/-0)
lib/lp/registry/model/milestone.py (+6/-0)
lib/lp/registry/templates/productrelease-add-from-series.pt (+7/-0)
lib/lp/registry/templates/productrelease-add.pt (+7/-0)
lib/lp/registry/tests/test_milestone.py (+14/-2)
Changed in launchpad: | |
assignee: | nobody → Aaron Bentley (abentley) |
status: | Triaged → In Progress |
Changed in launchpad: | |
assignee: | Aaron Bentley (abentley) → nobody |
status: | In Progress → Triaged |
Changed in launchpad: | |
assignee: | nobody → j.c.sackett (jcsackett) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
To be clear, proprietary projects should not be allowed to create a release. Embargoed should be allowed to, but with a warning issued that the release is public whether or not the project is. Embargoed projects may well want to release and then begin opening the project up, which we should support.