Re: 2018-03 CFM
От | Andrey Borodin |
---|---|
Тема | Re: 2018-03 CFM |
Дата | |
Msg-id | 65CE9E1F-E6A4-4A5F-B34F-673485F0A521@yandex-team.ru обсуждение исходный текст |
Ответ на | Re: 2018-03 CFM (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: 2018-03 CFM
|
Список | pgsql-hackers |
Hi, Michael! > 27 февр. 2018 г., в 6:34, Michael Paquier <michael@paquier.xyz> написал(а): > > On Mon, Feb 26, 2018 at 02:03:56PM -0500, Tom Lane wrote: >> David Steele <david@pgmasters.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. Maybe CF should be open if 2018-03 is in progress? Best regards, Andrey Borodin.
В списке pgsql-hackers по дате отправления: