Re: 2018-03 CFM

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Steele <david(at)pgmasters(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 2018-03 CFM
Date: 2018-03-07 06:56:01
Message-ID: 65CE9E1F-E6A4-4A5F-B34F-673485F0A521@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi, Michael!

> 27 февр. 2018 г., в 6:34, Michael Paquier <michael(at)paquier(dot)xyz> написал(а):
>
> On Mon, Feb 26, 2018 at 02:03:56PM -0500, Tom Lane wrote:
>> David Steele <david(at)pgmasters(dot)net> writes:
>>> I'm planning to fill the CFM role, unless there are objections.
>>
>> Thanks for volunteering!
>
> +1. I have also added a new commit fest entry marked as future, which
> will likely be used for 12 development:
> https://commitfest.postgresql.org/18/
> 2018-09 is a tentative name, please don't take that as a decided date as
> this will be discussed in Ottawa during the dev meeting.
>
> This matters for hackers as once a CF is marked as in-progress, there is
> no way to register a patch in it. And in the case of this March's CF,
> there would be no places where such future patches could go.

Actually, as for now, it is impossible to register patch at CF 2018-09. At least I do not see the "new patch" button. May be CF should be open if 2018-03 is in progress?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-03-07 07:00:46 Re: 2018-03 CFM
Previous Message Andrey Borodin 2018-03-07 06:50:55 GiST VACUUM