On Fri, Apr 6, 2018 at 6:59 PM, Jonathan S. Katz wrote:
> Best of luck to everyone over the next 24hrs!
I think that's the wrong sentiment, honestly. I think we have too
many committers relying way too much on luck already.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterpris
> On Apr 6, 2018, at 6:57 PM, Robert Haas wrote:
>
> On Fri, Apr 6, 2018 at 6:54 PM, Jonathan S. Katz wrote:
>> Yes. It follows the format from the previous ones, i.e:
>>
>> https://www.postgresql.org/message-id/ca+tgmoy56w5fozeeo+i48qehl+bsvtwy-q1m0xjuhucwggw...@mail.gmail.com
>
> I think m
On Fri, Apr 6, 2018 at 6:54 PM, Jonathan S. Katz wrote:
> Yes. It follows the format from the previous ones, i.e:
>
> https://www.postgresql.org/message-id/ca+tgmoy56w5fozeeo+i48qehl+bsvtwy-q1m0xjuhucwggw...@mail.gmail.com
I think my confusion resulted from the fact that my 2016 message said
"mu
> On Apr 6, 2018, at 6:53 PM, Robert Haas wrote:
>
> On Tue, Mar 27, 2018 at 9:51 AM, Jonathan S. Katz
> wrote:
>> The Release Management Team (RMT) for the PostgreSQL 11 release
>> has been assembled and has determined that the feature freeze date
>> for the PostgreSQL 11 release will be Apri
On Tue, Mar 27, 2018 at 9:51 AM, Jonathan S. Katz wrote:
> The Release Management Team (RMT) for the PostgreSQL 11 release
> has been assembled and has determined that the feature freeze date
> for the PostgreSQL 11 release will be April 7, 2018. This means that any
> feature that will be going in
Hi,
The Release Management Team (RMT) for the PostgreSQL 11 release
has been assembled and has determined that the feature freeze date
for the PostgreSQL 11 release will be April 7, 2018. This means that any
feature that will be going into the PostgreSQL 11 release must be
committed before 2018-04
