On Tue, May 26, 2026 at 6:22 AM Nikolay Samokhvalov <[email protected]> wrote: > > The slip risk, the N+1 marketing-renumbering precedent, and the possibility > that cadence may change (biannual or otherwise) -- all make sense. > > Year-tied version numbers don't fit. Let me propose something smaller that > still addresses the underlying user problem — knowing at a glance how old a > release is and when it goes EOL. > > I have another, much lighter proposal. In fact, two paths: > > 1) Docs. Add something like "Major version NN released YYYY, EOL Mon YYYY" > explicitly on pages like: > > https://www.postgresql.org/docs/ > https://www.postgresql.org/docs/release/ > https://www.postgresql.org/docs/current/index.html >
https://www.postgresql.org/docs/ After "PDF Version", add another column makes sense to me. > https://www.postgresql.org/docs/release/ > https://www.postgresql.org/docs/current/index.html For these two links, I'm not entirely sure where the best place to put that information would be.
