Neil,
> One approach would be to assign a committer to each patch, in addition
> to a reviewer (the committer and the reviewer might be the same, of
> course). Once the reviewer has signed off on the patch, the committer
> can do the final check over and commit.
Well, one thing I think we want to do by having non-committer reviewers, is
to not involve a committer at all if the patch is going to be sent back.
So one thing I was thinking of is:
1) change status to "ready for committer"
2) post message to -hackers detailing the review and calling for a
committer to check the patch
3) a committer picks it up
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco