Re: CommitFest status/management - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: CommitFest status/management
Date
Msg-id 4B149574.9020904@dunslane.net
Whole thread Raw
In response to Re: CommitFest status/management  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: CommitFest status/management  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Greg Smith wrote:
>
> If the need here is to speed up how fast things are fed to committers, 
> we can certainly do that.  The current process still favors having 
> reviewers do as much as possible first, as shown by all the stuff 
> sitting in the re-review queue.  The work we're waiting on them for 
> could be done by the committers instead if we want to shorten the 
> whole process a bit.  I don't think that's really what you want though.
>

As I have observed before, I think we need some infrastructure to help 
committers claim items, so we don't duplicate work.

Right now the only items marked "ready for reviewer" are Streaming 
Replication and Hot Standby, which I imagine Heiki will be handling.

I'm going to look at the YAML format for EXPLAIN patch shortly.

cheers

andrew




pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: CommitFest status/management
Next
From: Bruce Momjian
Date:
Subject: Re: SE-PgSQL patch review