There is no review list which can be sensibly driven to zero by a team

[James Westby]

+activereviews doesn't really work as a work queue. It would be awesome to have something that does (perhaps by tweaking +activereviews, perhaps by making a new page).

One way would be a paginated list under /people/+me showing:
 * Only Needs-review reviews
 * Things the person is reviewing which have either comments or new commits from the submitter.
 * Then things the person has been asked to review directly
 * Then things that a team they are in has been asked to review (with smaller teams first)
 * Oldest reviews first within those groups.

[Martin Pool (mbp)]

Why not just ask for activereviews to be batched?

- Martin

On 14/01/2010 3:00 PM, "James Westby"
<<email address hidden><jw%<email address hidden>>>
wrote:

Public bug reported:

This would be a page like +activereviews but would allow pagingation.

It would show the reviews requested for a person which were in "Needs
Review", sorting those which that person was directly asked to review above
those that were requested from a team that person is a member of. It would
then sort oldest first within those groups.

This would allow for pagination if done right, and so could be used for
large
teams.

Thanks,

James

** Affects: launchpad-code
    Importance: Undecided
        Status: New

--
Please create a +pendingreviews page
https://bugs.launchpad.net/bugs/507319
You received this bug notification because you are subscribed to
Launchpad Bazaar Integration.

[James Westby (james-w)]

On Thu, 14 Jan 2010 05:15:54 -0000, Martin Pool <email address hidden> wrote:
> Why not just ask for activereviews to be batched?

Paginating three sets is tough. Tim said that this would be a more
scalable approach. I think having more pages isn't great, but if the
existing one can't do what we need...

Thanks,

James

[Tim Penhey (thumper)]

On Thu, 14 Jan 2010 18:15:54 Martin Pool wrote:
> Why not just ask for activereviews to be batched?

There are six different lists on the active reviews page, which are determined
by interrogating the realized objects. This doesn't scale.

What is being proposed will only show reviews where the person (or team) has
been asked to review. Effectively a pure drive to zero list.

[Robert Collins (lifeless)]

Making +active reviews paginated may help with +activereviews pagination. I think a good starting point for this would be to make the sort order of each collection db backed, and use separate batching collections on the page. That would increase (but keep static) the number of queries, but each query would be simpler. This should still be able to be done efficiently, given that the point of a drive-to-zero queue is to be small.