milestone deactivation warning when milestone autocreated is alarming
Bug #386584 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Curtis Hovey |
Bug Description
When registering a release, and creating a milestone inline on the
format, you get a warning like: "The 0.0.1 milestone for this project
release was deactivated so that bugs and blueprints cannot be associated
with this release."
This warning is unnecessary and a little alarming (it has a /!\ marker)
as the milestone is only being created for the launchpad machinery of
using it to track the release.
-Rob
affects launchpad
--
Related branches
lp:~sinzui/launchpad/release-love
- Eleanor Berger (community): Approve
-
Diff: 262 lines (+73/-24)10 files modifieddatabase/schema/security.cfg (+3/-0)
lib/canonical/launchpad/subscribers/karma.py (+8/-2)
lib/lp/bugs/doc/malone-karma.txt (+32/-1)
lib/lp/registry/browser/productrelease.py (+0/-5)
lib/lp/registry/browser/tests/productrelease-views.txt (+0/-6)
lib/lp/registry/doc/milestone.txt (+23/-0)
lib/lp/registry/model/milestone.py (+6/-2)
lib/lp/registry/stories/productrelease/xx-productrelease-basics.txt (+0/-6)
lib/lp/registry/stories/productrelease/xx-productrelease-view.txt (+0/-1)
lib/lp/registry/templates/milestone-index.pt (+1/-1)
affects: | launchpad → launchpad-registry |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Agreed. The user does not care in this case.