On Thu, Sep 3, 2015 at 10:06 PM, Andres Freund <and...@anarazel.de> wrote: > To review (copying Heikki's message): > > 1. Pick a patch from the list at: > > https://commitfest.postgresql.org/6/ > > 2. Review it. Test it. Try to break it. Do we want the feature? Any > weird interactions in corner-cases? Does it have the intended or an > unintended performance impact? > > 3. Reply on the thread on pgsql-hackers with your findings. > > It is perfectly OK to review a patch that someone else has signed up for as > reviewer - different people tend to pay attention to different things.
We are close to the end of October, and the numbers are a bit more encouraging than at the beginning: Needs review: 27. Waiting on Author: 12. Ready for Committer: 5. Committed: 30 Among the five patches marked as ready for committer, one is a bug fix that should be back-patched (ahem). Shouldn't we move on with those entries first? Also, to all reviewers and authors, please be sure that the status of your patch is correctly updated. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
