Merge lp:~bac/launchpad/bug-638420 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Brad Crittenden |
Approved revision: | no longer in the source branch. |
Merged at revision: | 11552 |
Proposed branch: | lp:~bac/launchpad/bug-638420 |
Merge into: | lp:launchpad |
Diff against target: |
79 lines (+0/-34) 2 files modified
lib/lp/registry/browser/tests/pillar-views.txt (+0/-29) lib/lp/registry/templates/pillar-involvement-portlet.pt (+0/-5) |
To merge this branch: | bzr merge lp:~bac/launchpad/bug-638420 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Edwin Grubbs (community) | code | Approve | |
Review via email: mp+35477@code.launchpad.net |
Commit message
Enable project configuration progress bars on lpnet.
Description of the change
= Summary =
The roll-out of the progress bar was blocked from lpnet originally as it
wasn't accurate. It should be presented in the 10.10 release.
== Proposed fix ==
Remove the template-based traps that prevented the progress bar and
yes/no indicators from rendering.
The test was changed to demonstrate that the progress bar does show up
in lpnet. But, that test makes no sense going forward so the entire
section was removed.
== Pre-implementation notes ==
None
== Implementation details ==
As above.
== Tests ==
bin/test -vvt pillar-views.txt
== Demo and Q/A ==
Look at project home page (for a project you own) on production and see
the progress bar.
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
Hi Brad,
This looks good.
-Edwin