Re: Just for fun: Postgres 20? - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Just for fun: Postgres 20?
Date
Msg-id CAFNqd5VhbVcs8CCczBtRUhXX1CVhU3NpV7RfWiWZ3icc-suFnA@mail.gmail.com
Whole thread Raw
In response to Re: Just for fun: Postgres 20?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Just for fun: Postgres 20?  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
On Wed, 12 Feb 2020 at 08:28, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
marcelo zen escribió:
> I'd rather have releases being made when the software is ready and not when
> the calendar year mandates it.
> It seems like a terrible idea.

But we do actually release on calendar year.  While it seems not
unreasonable that we might fail to ship in time, that would likely lead
to one month, two months of delay.  Four months?  I don't think anybody
even imagines such a long delay.  It would be seen as utter,
unacceptable failure of our release team.

All said, I think there's some merit to avoiding a PostgreSQL 13 release, because
there's enough superstition out there about the infamous "number 13."

Perhaps we could avert it by doing an "April Fool's Postgres 13" release?
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Wait event that should be reported while waiting for WAL archiving tofinish
Next
From: Fujii Masao
Date:
Subject: Re: Exposure related to GUC value of ssl_passphrase_command