From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: September 2015 Commitfest |
Date: | 2015-10-30 13:02:34 |
Message-ID: | CA+TgmoZRfZ=3jv9mKHeqghr7tN=Gr2bqEAWmOvRaZFvKV+ZZDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 30, 2015 at 10:47 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Oct 22, 2015 at 9:21 AM, Andres Freund wrote:
>>> 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?
>>
>> I think at this point we essentially can just move all entries to the
>> next. Will do that, and note down which patches haven't gotten any real
>> review.
>
> We are close to the end of the month. Should I move on to do the
> vacuuming or are you planning to do it? At this stage, to be fair with
> people whose patches are in "waiting on author" state and because
> there is not much time until the next CF begins, I propose to remove
> all the remaining 43 entries with the same status as currently listed:
> Needs review: 26. Waiting on Author: 11. Ready for Committer: 6.
Gosh, that's a lot of stuff that didn't get reviewed. :-(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Zeus Kronion | 2015-10-30 13:04:29 | Re: WIP: Fix parallel workers connection bug in pg_dump (Bug #13727) |
Previous Message | Andres Freund | 2015-10-30 12:59:59 | Re: [ADMIN] Replication slots and isolation levels |