Merge lp:~julian-edwards/launchpad/publish-warning-bug-715116 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Julian Edwards |
Approved revision: | no longer in the source branch. |
Merged at revision: | 12350 |
Proposed branch: | lp:~julian-edwards/launchpad/publish-warning-bug-715116 |
Merge into: | lp:launchpad |
Diff against target: |
127 lines (+70/-3) 3 files modified
lib/lp/soyuz/browser/archive.py (+18/-2) lib/lp/soyuz/browser/tests/test_archive_packages.py (+49/-0) lib/lp/soyuz/interfaces/archive.py (+3/-1) |
To merge this branch: | bzr merge lp:~julian-edwards/launchpad/publish-warning-bug-715116 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Leonard Richardson (community) | Approve | ||
Review via email: mp+48952@code.launchpad.net |
Commit message
[r=leonardr][bug=715116] Add a big informational notice on the PPA pages if publishing is disabled.
Description of the change
= Summary =
Fix bug 715116
== Proposed fix ==
A PPA can have apparently "stuck" publications and if it's private, stuck
builds, if someone has turned the publishing flag off.
This branch adds a big informational notice on the PPA pages if the publishing
is disabled.
== Implementation details ==
There's three different message segments added depending on some criteria:
* The basic "publishing is disabled" if that's the case
* Add a link to "Change details" if the requesing user has lp.edit
* Add a message about stuck builds if the PPA is private.
As a bonus, fix the really crappy description text on the "publish" flag on
the +edit page.
== Tests ==
bin/test -cvv test_archive_
== Demo and Q/A ==
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
lib/lp/
./lib/lp/
586: E301 expected 1 blank line, found 0
714: E301 expected 1 blank line, found 0
737: E301 expected 1 blank line, found 0
760: E301 expected 1 blank line, found 0
860: E301 expected 1 blank line, found 0
894: E501 line too long (84 characters)
894: Line exceeds 78 characters.
The code and tests look good but I think the wording has some problems. Let me nitpick your wording to try and save you a full UI review.
1. "Publishing has been disabled for this archive" is a full sentence and needs a period after it.
2. "Go to the Change details page..." is also a full sentence sentence.
3. Should "no builds will be dispatched" be "no builds are being dispatched"? Isn't it something that's (not) happening continuously, right now?
4. I'm not happy with the wording "Go to the Change details page", or with sticking a "Note:" in there with no special markup. How about one of these:
"Publishing has been disabled for this archive. Since this archive is private, no builds are being dispatched. You can <a>re-enable publishing</a>."
"Publishing has been disabled for this archive. <a>(Re-enable it.)</a> Since this archive is private, no builds are being dispatched."
What do you think?
I also don't understand why "no builds are being dispatched" follows from "this archive is private". Why are builds dispatched for public archives that have publishing disabled? Will the actual users understand?