From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Commit fest status for 2015-11 |
Date: | 2015-12-24 03:09:03 |
Message-ID: | CAB7nPqQCn_PAKVvFr9GuzxEnj4pZ1WyTBp=2EKcn1tJ+EUjfkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 22, 2015 at 10:45 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Tue, Dec 22, 2015 at 4:04 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> OK, if those don't get addressed soon, they will be moved to the next
>> CF with the same status.
>
> After a first pass, Numbers are getting down, I am just too tired to continue:
> Needs review: 13.
> Waiting on Author: 15.
> Ready for Committer: 5
>
> Two additional patches have been marked as ready for committer:
> 1) Bug fix for pg_dump --jobs when password is passed a a parameter in
> a connection string:
> https://commitfest.postgresql.org/7/405/
> 2) Default roles, in Stephen's plate:
> https://commitfest.postgresql.org/7/49/
I had a look at all the remaining entries and treated each one of
them, patches marked as ready for committer have been moved to next CF
with the same status. There are currently 3 remaining entries in the
CF app where it would be cool authors and/or reviewers give a status
of the situation. Once this is addressed the CF of 2015-11 will be
closed.
Note particularly to authors: if your patch has been returned with
feedback, but you are still working on it, please make sure that it is
moved to next CF soon. Or, if your patch has been moved to next CF,
*but* you are not working on it, it would be nice to mark it as
returned with feedback in 2016-01.
Thanks.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2015-12-24 03:24:45 | Re: COPY FREEZE and PD_ALL_VISIBLE |
Previous Message | Michael Paquier | 2015-12-24 03:05:09 | Re: PATCH: index-only scans with partial indexes |