Development focus isn't explained usefully
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Unassigned |
Bug Description
The form control for specifying which series is a project's development focus has the label "Development focus", and the caption "The 'trunk' series where development is focused".
That's not a useful explanation. If it really is "the 'trunk' series", why does Launchpad let you set it to a series other than "trunk"? And why does Launchpad need to know in the first place?
It turns out that changing the development focus (a) changes what "bzr branch lp:project-name" does, and (b) makes a bug report say "Tracked in <name of development series>" for the project-in-general if the bug is recorded as occurring in the development focus series in particular. (Thanks to Paul Hummer and Graham Binns for these explanations.)
The caption should be reworded to explain what the development focus actually does.
Related branches
- Graham Binns (community): Approve (code)
-
Diff: 124 lines (+24/-8)6 files modifiedlib/lp/registry/browser/distroseries.py (+5/-2)
lib/lp/registry/browser/tests/distroseries-views.txt (+10/-0)
lib/lp/registry/interfaces/product.py (+4/-1)
lib/lp/registry/stories/product/xx-product-edit.txt (+2/-2)
lib/lp/registry/stories/productseries/xx-productseries-series.txt (+1/-1)
lib/lp/registry/templates/productseries-macros.pt (+2/-2)
description: | updated |
Changed in launchpad-registry: | |
milestone: | series-future → 10.05 |
assignee: | nobody → Curtis Hovey (sinzui) |
status: | Triaged → In Progress |
tags: | added: trivial |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
assignee: | Curtis Hovey (sinzui) → nobody |
This can be addressed in the work to unify series, milestones, and releases.