Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
Subject: Re: Reports on obsolete Postgres versions
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <20240312013756.GB1787866@nathanxps13>
Date: Tue, 12 Mar 2024 11:00:19 +0100
Cc: Bruce Momjian <bruce@momjian.us>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 "Jonathan S. Katz" <jkatz@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C6CBFF3-21FE-4707-A5D1-C399B28DF50A@yesql.se>
References: <Ze9rnSQ4jAOpvF7k@momjian.us>
 <20240311211204.GA1786481@nathanxps13> <Ze902XsAC85dizNP@momjian.us>
 <20240312013756.GB1787866@nathanxps13>
To: Nathan Bossart <nathandbossart@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/6C6CBFF3-21FE-4707-A5D1-C399B28DF50A%40yesql.se>
Precedence: bulk

> On 12 Mar 2024, at 02:37, Nathan Bossart <nathandbossart@gmail.com> =
wrote:
>=20
> On Mon, Mar 11, 2024 at 05:17:13PM -0400, Bruce Momjian wrote:
>> On Mon, Mar 11, 2024 at 04:12:04PM -0500, Nathan Bossart wrote:
>>> I've read that the use of the term "minor release" can be confusing. =
 While
>>> the versioning page clearly describes what is eligible for a minor =
release,
>>> not everyone reads it, so I suspect that many folks think there are =
new
>>> features, etc. in minor releases.  I think a "minor release" of =
Postgres is
>>> more similar to what other projects would call a "patch version."
>>=20
>> Well, we do say:
>>=20
>> 	While upgrading will always contain some level of risk, =
PostgreSQL
>> 	minor releases fix only frequently-encountered bugs, security =
issues,
>> 	and data corruption problems to reduce the risk associated with
>> 	upgrading. For minor releases, the community considers not =
upgrading to
>> 	be riskier than upgrading.=20
>>=20
>> but that is far down the page.  Do we need to improve this?
>=20
> I think making that note more visible would certainly be an =
improvement.

We have this almost at the top of the page, which IMHO isn't a very good
description about what a minor version is:

	Each major version receives bug fixes and, if need be, security =
fixes
	that are released at least once every three months in what we =
call a
	"minor release."

Maybe we can rewrite that sentence to properly document what a minor is =
(bug
fixes *and* security fixes) with a small blurb about the upgrade risk?

(Adding Jonathan in CC: who is good at website copy).

--
Daniel Gustafsson