• 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 archive 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? That would affect the design too.

You can also view the input information regarding this page.

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.

Performance restrictions

To enable a larger set of uploads to be included while bulk-reviewing, the resulting binaries for each upload (with any relevant 'old' publishing info) can be loaded into the page *after* the initial page load. There are several options for how this could be done, the most obvious being to include an 'expand all' option both at the top of the page as well as for each source package release grouping. Another option would be to automatically load in the expanded info as soon as the initial page has loaded, but hopefully that's not necessary?

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 latest (max) upload date of the grouped uploads)

A typical NEW review

Joe picks a source package name from the top of the new queue and hits 'o' to open the source package, displaying all the binaries. He checks the current overrides for each binary - which all look sane. (Where does the downloading of the packages happen? how can the web ui help there?). Joe hits 'a' to mark all the binaries for that source package as accepted. The phone rings, so rather than moving to the next review Joe just hits enter to accept the one package that he's reviewed.

Overriding one or more uploads

While reviewing the uploads for 50 source package releases, one particular source package release near the bottom of the list catches Martin's attention - he clicks (keys?) 'Expand all' for that source package release which loads in the resulting binaries for all the binary uploads, as well as any previous old publishings of the same binary from other packages. Martin notices that one of the resulting binaries has been published in main in the past via a different source package, and so updates the destination of the new binary to main.

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 binary uploads for each source package release with the resulting binaries 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>.

Approving uploads

For stable release updates and times when the development release gets frozen for release preparations, Martin looks at the "unapproved" queue. Clicking on the first source package opens the .changes file, from where the LP bug numbers are clickable links to the bug reports. Then he clicks on "diff to previous version" which gives him a debdiff to the version currently published in the corresponding pocket. He marks the checkbox, clicks Accept or Reject based on the decision, and then starts the process again until the queue is empty.

Bulk-accepting a bunch of debian imports

After feedback from Martin this is not a valid use-case as there are well established processes for this.

Questions

• I wonder if it would be handy to reject certain binaries inline - so it disappears immediately from the queue? I'm assuming that currently, if someone selects all, then deselects one or two, accepts all the select uploads, they would then need to go manually navigate the list again to select and reject the uploads that they previously deselected.
• Is the workflow substantially different for reviewing source uploads vs binary uploads? Or is it easy to bulk-review a mixed list of source/binary uploads.
• Have there ever been concurrency issues with doing bulk reviewing of the queue (multiple people reviewing the same uploads)? Or perhaps the latest review would just over-write?