public inbox for [email protected]
help / color / mirror / Atom feedFrom: Philip Alger <[email protected]>
To: pgsql-hackers <[email protected]>
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
Date: Sun, 24 May 2026 12:31:55 -0500
Message-ID: <CAPXBC8LibVcuxiLoo_c2DLTmNh3sN0soyyGgRcdeKX8Zdpd5qw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAM527d9HNDGS4wZBNK8vhRXtRX09i4UwKjvifUvSPS+P-i-1CQ@mail.gmail.com>
<CACLU5mSnxYVf1ZkuZ4VuiREXA_42fe22+fR38y2_JJ6+WJQGyw@mail.gmail.com>
<CAMsGm5fPUwBxgY2RGGzpEp7Sjv7VMU28vcjN+RmuWQpTWM2uRA@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
> > On 22.05.26 08:54, Tom Lane wrote:
> >> I don't like either version of this proposal, because I fear it
> >> puts way too much faith in our ability to adhere to a fixed release
> >> calendar. What happens if "v2027" slips into 2028? Are we then
> >> unable to resume the normal schedule for the following release?
>
> A different angle came up in the AI-focused unconference session at
> PGConf.dev: somebody speculated that use of AI might accelerate our
> development cycle to the point where it'd be sensible to have two
> major releases per year.
>
Not only these points, but if a release occurs in December, the version
will seem outdated once the new year arrives in ~31 days. Users or
enterprises will feel compelled, or pressured, to upgrade because the name
will appear ancient to their clients if they are using v2025, for example.
-1 on using the year.
--
Best,
Phil Alger
EDB: https://www.enterprisedb.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
In-Reply-To: <CAPXBC8LibVcuxiLoo_c2DLTmNh3sN0soyyGgRcdeKX8Zdpd5qw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox