Hard to find related branches when composing recipe
Bug #670452 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
I recently went to make a daily build recipe for testtools. The project on Launchpad is linked to its source package, which has branches.
When composing a recipe, I would like to be pointed the source package branch if it exists. Perhaps it would also be useful to mention other branches used in other recipes for the branch we're coming from.
Related branches
lp:~wallyworld/launchpad/recipe-find-related-branches
- Tim Penhey (community): Approve
- Steve Kowalik (community): Approve (code*)
- Curtis Hovey (community): Approve (ui)
- Guilherme Salgado (community): Needs Information (ui*)
-
Diff: 969 lines (+732/-6)8 files modifiedlib/lp/code/browser/sourcepackagerecipe.py (+77/-3)
lib/lp/code/browser/tests/test_sourcepackagerecipe.py (+246/-2)
lib/lp/code/interfaces/branchtarget.py (+30/-1)
lib/lp/code/model/branchtarget.py (+88/-0)
lib/lp/code/model/tests/test_branchtarget.py (+60/-0)
lib/lp/code/templates/sourcepackagerecipe-new.pt (+3/-0)
lib/lp/code/templates/sourcepackagerecipe-related-branches.pt (+75/-0)
lib/lp/testing/factory.py (+153/-0)
lp:~wallyworld/launchpad/recipe-related-branches-layout
- Robert Collins (community): Approve
- Tim Penhey: Pending requested
-
Diff: 19 lines (+2/-2)1 file modifiedlib/lp/code/templates/sourcepackagerecipe-related-branches.pt (+2/-2)
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
Revision history for this message
| Jonathan Lange (jml) wrote Re: [Bug 670452] Re: Hard to find related branches when composing recipe | #2 |
| Changed in launchpad-code: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote Bug fixed by a commit | #3 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| j.c.sackett (jcsackett) wrote | #4 |
| tags: |
added: qa-ok removed: qa-needstesting |
| tags: |
added: qa-bad removed: qa-ok |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
| Changed in launchpad: | |
| milestone: | none → 11.01 |
| Changed in launchpad: | |
| status: | Fix Released → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #6 |
| Changed in launchpad: | |
| milestone: | 11.01 → 11.02 |
| tags: |
added: qa-needstesting removed: qa-ok |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #7 |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
How do you envision this?
We could do something like have an expandable section below the text for "Possibly relevant branches..." (or something), and have links to series branches and package branches for the related package.
What do you think?