'expected' field is not very interesting after a release is made
Bug #386586 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Curtis Hovey |
Bug Description
e.g. on https:/
field is both empty and not interesting. It would look nicer to me to
hide it.
affects launchpad
--
Related branches
lp:~sinzui/launchpad/release-love
Merged
into
lp:launchpad
- 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: | |
milestone: | none → 10.01 |
assignee: | nobody → Curtis Hovey (sinzui) |
status: | Triaged → In Progress |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hiding it will introduce consistence that the user must guess what is happening. I think we should be setting the expected date to the release date when the milestone is created by the add release form.