On Tue, Sep 22, 2026 at 08:37:42AM +0200, Daniel Gustafsson wrote: > > On 22 Sep 2026, at 07:51, Laurenz Albe <[email protected]> wrote: > > > I have no right to burden committers even more, but I'd say that such > > changes > > should be part of the commit message. > > Not commenting on the specific commit or change here, but in general I think > it > would be good if we started adding incompatibilities and upgrade notes to the > release notes over the development cycle rather than trying to collect them at > the end. It's fine to add a rough text which can be copy edited (or even > removed if deemed too minor) as the release notes process takes place, but > having it in the same commit as the change should ideally mean less work at > the > end of the cycle and fewer missed notes.
Actually, many committers already mark incompatibilities and mention the release notes in their commit messages. My question here is whether error code changes are incompatibilities worthy of being mentioned in the release notes, and if committers don't mention this in the commit message, how would I find them when creating the release notes? I wonder if this should be discussed on hackers instead? -- Bruce Momjian <[email protected]> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
