Merge lp:~jcsackett/launchpad/mirrors-tell-where-they-live-652134 into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Gavin Panella on 2010-10-08 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11722 |
| Proposed branch: | lp:~jcsackett/launchpad/mirrors-tell-where-they-live-652134 |
| Merge into: | lp:launchpad |
| Diff against target: |
125 lines (+57/-9) 4 files modified
lib/lp/code/browser/tests/test_product.py (+22/-0) lib/lp/code/stories/branches/xx-product-branches.txt (+10/-3) lib/lp/code/templates/product-branch-summary.pt (+22/-5) lib/lp/registry/model/product.py (+3/-1) |
| To merge this branch: | bzr merge lp:~jcsackett/launchpad/mirrors-tell-where-they-live-652134 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Gavin Panella (community) | 2010-10-08 | Approve on 2010-10-08 | |
|
Review via email:
|
|||
Commit Message
Updates imported branches on products to display upstream information and present as EXTERNAL codehosting_usage.
Description of the Change
Summary
=======
Updates presentation of products with an imported development focus branch to
reflect a codehosting_usage of EXTERNAL, not NOT_APPLICABLE, and to show
the appropriate upstream data.
Proposed fix
============
Update the product code index page to show the upstream information if the
development focus branch is imported.
Pre-implementation notes
=======
Spoke with Curtis Hovey.
Implementation details
=======
Largely as in Proposed; however, the branch also corrected the
codehosting_usage enum to display a branch_type of IMPORTED as a
ServiceUsage of EXTERNAL. Previously it was NOT_APPLICABLE.
Tests
=====
bin/test -t code.*external_
Demo and Q/A
============
In launchpad.dev, add the gnome-terminal/
for gnome-terminal; gnome-terminal should show the upstream links for the
branch.
Lint
====
make lint output:
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
lib/lp/
| j.c.sackett (jcsackett) wrote : | # |
> Looks good, only one comment:
>
> + # Test that the correct information is shown for an import
>
> I think the style here should be more declarative (if that's the right
> term), so something like:
>
> The correct information is shown for an import.
>
> It's probably worth explaining what's being tested rather than only
> saying "correct information", unless it's easier to read the test than
> to describe. Something like:
>
> The page for an imports of an external branch includes an
> explanation of where it came from and what it can be now be used
> for.
I have replaced the test comment with a better one per your suggestion. Thanks!

Looks good, only one comment:
+ # Test that the correct information is shown for an import
I think the style here should be more declarative (if that's the right
term), so something like:
The correct information is shown for an import.
It's probably worth explaining what's being tested rather than only
saying "correct information", unless it's easier to read the test than
to describe. Something like:
The page for an imports of an external branch includes an
explanation of where it came from and what it can be now be used
for.