| 2010-12-15 03:45:51 |
Paul Sladen |
bug |
|
|
added bug |
| 2010-12-15 09:28:09 |
Julian Edwards |
soyuz: status |
New |
Triaged |
|
| 2010-12-15 09:28:11 |
Julian Edwards |
soyuz: importance |
Undecided |
Low |
|
| 2010-12-15 09:28:34 |
Julian Edwards |
summary |
"Start in 1 minute" shown for hours despite 12505 points |
The PPA page should warn if publication is turned off |
|
| 2010-12-15 09:28:52 |
Julian Edwards |
tags |
|
bugjam2010 ppa trivial ui |
|
| 2010-12-15 09:34:01 |
Paul Sladen |
description |
I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority. |
I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority.
See also bug #690561 for fixing the help text to the "Publish" button to state what it actually does. |
|
| 2010-12-15 09:36:21 |
Paul Sladen |
description |
I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority.
See also bug #690561 for fixing the help text to the "Publish" button to state what it actually does. |
I did an upload that scored as private+partner+low (=12505 score) and the Launchpad frontend takes account of this displaying:
"Start in 1 minute" (12505)
however, even after hour(s) the package still remains "Start in 1 minute". I personally don't mind when it gets built, but I'm wondering if there's a disconnect between the frontend and backend priority mechanisms. Ideally the "1 minute" should either be replaced with the estimated length of the queue (at insertion time), or a higher-priority job should get the higher priority.
See also bug #690561 for fixing the help text next to the "Publish" button to state what it actually does.
|
|
