Would be nice to have UI indication of upload status.

Bug #32405 reported by Adam Conrad
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Julian Edwards

Bug Description

It would be nice if the source/version and binary build status pages could be updated with an upload's status in the queue, so as an upload passes through UNCHECKED/UPLOADED (whatever you want to call it), to NEW/REJECTED/ACCEPTED/etc, we have a clear indication of where the sources/binaries are.

For sources, this isn't as critical, since uploaders get email telling them when they're trapped in NEW or REJECTED, etc, but for binary uploads from the buildds, there's no way for an average joe to know what's happened to a build after it's successfully built, without asking an ftpmaster to hunt it down for them (which can be a serious drain on their time).

Revision history for this message
Celso Providelo (cprov) wrote :

Right, I think we can extend the "succesfully built" (build status) information to aggregate the current queue status, so built packages will be displayed as:
{{{
 foo-1.0 dapper i386 - Succesfully Built (NEW)
 bar-1.1 dapper powerpc - Succesfully Built (ACCEPTED)
 boggus-1.9 dapper amd64 - Succesfully Built (REJECTED)
}}}

It doesn't affect other build states than the "BUILT", AFAYCS. What do you think ?

Changed in soyuz:
assignee: nobody → cprov
status: Unconfirmed → Confirmed
Changed in soyuz:
importance: Medium → High
Changed in soyuz:
assignee: cprov → julian-edwards
Changed in soyuz:
status: Confirmed → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Fixed in RF 4895.

Changed in soyuz:
status: In Progress → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.