Do we ever edit release notes after release to add warnings about incompatibilities?

From: Greg Stark <stark(at)mit(dot)edu>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Do we ever edit release notes after release to add warnings about incompatibilities?
Date: 2020-02-21 21:14:57
Message-ID: CAM-w4HOKxwqY0rQaO0HPB=yir6OrvkQMK3ex8zhwOH+Nwpg70g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

So last year in 10.5, 9.6.10, 9.5.9, 9.4.19, and 9.3.24 we had a
binary ABI break that caused pglogical and other logical decoding
plugins to break:

https://github.com/2ndQuadrant/pglogical/issues/183#issuecomment-417558313

This wasn't discovered until after the release so the release notes
don't highlight the risk. Someone upgrading past this release now
could diligently read all the release notes for all the versions they
care about and would never see anything warning that there was an
unintentional ABI break.

I wonder if we shouldn't be adding a note to those release notes after
the fact (and subsequent "However if you are upgrading from a version
earliers than...." notes in later releases). It would be quite a pain
I'm sure but I don't see any other way to get the information to
someone upgrading in the future. I suppose we could just add the note
to the current release notes on the theory that we only support
installing the current release.

--
greg

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2020-02-21 21:40:04 Re: Do we ever edit release notes after release to add warnings about incompatibilities?
Previous Message Peter Eisentraut 2020-02-21 21:03:42 Re: allow running parts of src/tools/msvc/ under not Windows