From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | marcelo zen <mzen(at)itapua(dot)com(dot)uy>, Andreas Joseph Krogh <andreas(at)visena(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Just for fun: Postgres 20? |
Date: | 2020-02-12 17:32:27 |
Message-ID: | CAFNqd5VhbVcs8CCczBtRUhXX1CVhU3NpV7RfWiWZ3icc-suFnA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 12 Feb 2020 at 08:28, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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?"
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2020-02-12 17:37:29 | Re: Exposure related to GUC value of ssl_passphrase_command |
Previous Message | Fujii Masao | 2020-02-12 17:29:20 | Wait event that should be reported while waiting for WAL archiving to finish |