Re: Commit fest 2017-11 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Commit fest 2017-11
Date
Msg-id CAB7nPqSrxaFKERokZEMk4wSO1i-FwbqfU1JoZKRs8aMSJLktjw@mail.gmail.com
Whole thread Raw
In response to Re: Commit fest 2017-11  (Michael Paquier <michael.paquier@gmail.com>)
Responses RE: Commit fest 2017-11
Re: Commit fest 2017-11
List pgsql-hackers
On Tue, Nov 28, 2017 at 11:28 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> The current commit fest is coming to an end, and as many may have
> noticed, I have begun classifying patches depending on their status.
> This will likely take a couple of days. As a last push, I would like
> to point out that there are 22 patches marked as ready for committer:
> https://commitfest.postgresql.org/15/?status=3.

All patches not marked as ready for committer have been classified, by
either being marked as returned with feedback or moved to the next CF.
I may have made some mistakes of course, hence if you feel that the
status of your patch is not appropriate, feel free to update it as you
think is best-suited.

I would like to point out that the status of each patch on the CF app
was rather representative to the status on their respective thread
(only a couple had incorrect statuses, at least I thought so), and
that's a nice improvement. One thing that could be improved in my
opinion is that patch authors should try more to move a patch to a
following commit fest once the end gets close...This would leverage
slightly the load of work for the CFM.

Remains 22 patches as of now, exactly *one* for each committer. Thanks
Fabien for pointing that out to me :)
-- 
Michael


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] <> join selectivity estimate question