public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Tom Lane <[email protected]>
To: Isaac Morland <[email protected]>
Cc: Kirk Wolak <[email protected]>
Cc: Nikolay Samokhvalov <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
Date: Sun, 24 May 2026 16:22:47 +0200
Message-ID: <[email protected]> (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]>

On 22.05.26 08:54, Tom Lane wrote:
> Isaac Morland <[email protected]> writes:
>> I like this because it makes it very clear that there has been a change in
>> numbering scheme. Skipping 7 numbers could be due to almost anything, in
>> the long term, but no one will think PG2026 is just 2008 versions after
>> PG18. Also, I agree that while most likely no one on this list will be
>> worrying about this in 2100, it would be nice to know that nobody has to
>> worry about what comes after PG99.
> 
> Geez, I thought we were permanently done with what-shall-we-call-
> the-next-release threads after we dropped three-part version numbers.
> 
> 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?

Furthermore, some things that release toward the end of year N are 
released as version N+1, for marketing reasons.  So this approach 
wouldn't even really reduce ambiguity or the need for more arguing.

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], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Rename Postgres 19 to Postgres 26 (year-based)?
  In-Reply-To: <[email protected]>

* 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