On Oct 30, 2025, at 16:10, Robert Haas <[email protected]> wrote:
> Said differently, if somebody > nukes the ABI history file from a back-branch, I think we should > assume that represents a deliberate decision on the part of the > project to stop caring about ABI compatibility in that particular > back-branch, not an error that the build-farm needs to flag. I was thinking less of old branches than brand new ones. I’m on board with requiring an ABI history file, and that it’s part of the branch for release process to create one should minimize the chances that someone forgets long enough for an ABI change to go uncaught and released. Best, David
signature.asc
Description: Message signed with OpenPGP
