• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Purpose

The /distribution/series/+queue page should enable buildd admins to accept, override and reject packages in bulk, providing quick access to all the information necessary for the decision.

? Is part of the purpose also for uploaders to check progress?

Target user audience

• The primary users of this page are technically very adept Launchpad users / admins who will prefer a console script if it gets the job done faster.

Use-cases

(Note: these use-cases are with the assumption that we'll be able to group by source package release and order by the max upload date of the grouped uploads)

Bulk-accepting a bunch of debian imports

Colin opens '/ubuntu/karmic/+queue' and sees that there are currently over fifty source package releases with related binaries in the queue. Noticing that nearly all of the packages are debian imports, Colin tabs to 'select all' (the first form input) and hits <SPACE> to select all the binaries associated with the listed source package releases. He then tabs down through the list deselecting the two packages that are not debian imports, tabs to the Accept button and hits <ENTER>.

Excluding one binary from the review

Rob opens '/ubuntu/karmic/+queue' and sees that there are quite a few packages requiring closer inspection. He tabs to 'Expand all' which immediately begins expanding the source package releases with the related binary debs and existing overrides information. Rob works his way down the list, checking the box next to the source package release for some packages (which automatically selects all the binaries) and manually selecting certain binaries for others. When he reaches the bottom of the list, he tabs to the Accept button and hits <ENTER>

Questions

• What information is *always* necessary? and progressively, what information is needed to make a more detailed judgement. (Specifically, I'm wondering if there is ever a case that the group source-package-release would be enough, or whether we always want to see the binaries uploads and just load in output debs with Colin's existing overrides (OLD rows) dynamically)
• I wonder if it would be handy to reject certain binaries inline - so it disappears immediately from the queue? Currently I'm not sure what people do after selecting some uploads - how are the non-selected ones rejected? Manually going through the list again after the page reloads to reject those ones?
• I'm assuming from the current UI that different binaries for the same source package can have different destinations even though they typically do not. Is this the case? (seems to be confirmed by comment in Colin's mail: "one is reduced to checking each binary upload individually rather than together with its typically nearly identical fellows for other architectures")
• Have there ever been concurrency issues with doing bulk reviewing of the queue? Or perhaps the latest review would just over-write?