pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
create .abi-compliance-history file for v19
4+ messages / 3 participants
[nested] [flat]

Commits from this thread:
  2026-11-17 898f60dd75  Add .abi-compliance-history to v19 branch.
* create .abi-compliance-history file for v19
@ 2026-11-17 16:42 Nathan Bossart <nathandbossart@gmail.com>
  2026-11-17 22:39 ` Re: create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Nathan Bossart @ 2026-11-17 16:42 UTC (permalink / raw)
  To: pgsql-hackers

I see that we haven't done $subject yet, so here's a patch.  Assuming there
are no objections, I'll plan to apply it once the freeze is lifted
(although this particular change probably needn't be subject to the
freeze).

-- 
nathan

Attachments:

v1-0001-Create-.abi-compliance-history-file-for-v19.patch (text/plain, 1.7K) download From 0e871ed7b44996bbd3f7eaac10f251057bfaca99 Mon Sep 17 00:00:00 2001 From: Nathan Bossart <nathan@postgresql.org> Date: Tue, 17 Nov 2026 10:35:01 -0600 Subject: [PATCH v1 1/1] Create .abi-compliance-history file for v19. --- .abi-compliance-history | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 .abi-compliance-history diff --git a/.abi-compliance-history b/.abi-compliance-history new file mode 100644 index 00000000000..2e63788a64f --- /dev/null +++ b/.abi-compliance-history @@ -0,0 +1,26 @@ +# Reference point for ABI compliance checks +# +# This file lists commits on the current branch that break ABI compatibility in +# ways that have been deemed acceptable (e.g., removing an extern function with +# no third-party uses). The primary intent of this file is to control the ABI +# compliance checks on the buildfarm, but it also serves as a central location +# to document the justification for each. +# +# In general, entries should be added reactively after an abi-compliance-check +# buildfarm failure. It is important to verify the details of the breakage +# match expectations, as the first entry listed will become the updated ABI +# baseline point. +# +# Add new entries by adding the output of the following to the top of the file: +# +# $ git log --pretty=format:"%H%n#%n# %s%n# %cd%n#%n# <ADD JUSTIFICATION HERE>" $ABIBREAKGITHASH -1 --date=iso +# +# Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and +# why it is deemed acceptable. + +5c839a2a08b9b87a349be97371fac6c5a2873b10 +# +# Stamp 19.0. +# 2026-11-16 15:02:58 -0500 +# +# This is the original ABI baseline point for REL_19_STABLE. -- 2.55.0
^ permalink raw reply [nested|flat] 4+ messages in thread

* Re: create .abi-compliance-history file for v19
  2026-11-17 16:42 create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
@ 2026-11-17 22:39 ` Nathan Bossart <nathandbossart@gmail.com>
  2026-11-18 02:22   ` Re: create .abi-compliance-history file for v19 Andrew Dunstan <andrew@dunslane.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Nathan Bossart @ 2026-11-17 22:39 UTC (permalink / raw)
  To: pgsql-hackers

On Tue, Nov 17, 2026 at 10:42:48AM -0600, Nathan Bossart wrote:
> I see that we haven't done $subject yet, so here's a patch.  Assuming there
> are no objections, I'll plan to apply it once the freeze is lifted
> (although this particular change probably needn't be subject to the
> freeze).

This is now done.

-- 
nathan






^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: create .abi-compliance-history file for v19
  2026-11-17 16:42 create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
  2026-11-17 22:39 ` Re: create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
@ 2026-11-18 02:22   ` Andrew Dunstan <andrew@dunslane.net>
  2026-11-18 02:24     ` Re: create .abi-compliance-history file for v19 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Andrew Dunstan @ 2026-11-18 02:22 UTC (permalink / raw)
  To: Nathan Bossart <nathandbossart@gmail.com>; +Cc: pgsql-hackers




> On Nov 17, 2026, at 5:39 PM, Nathan Bossart <nathandbossart@gmail.com> wrote:
> 
> On Tue, Nov 17, 2026 at 10:42:48AM -0600, Nathan Bossart wrote:
>> I see that we haven't done $subject yet, so here's a patch.  Assuming there
>> are no objections, I'll plan to apply it once the freeze is lifted
>> (although this particular change probably needn't be subject to the
>> freeze).
> 
> This is now done.
> 

Should this be added to release procedures?

Cheers

Andrew 





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: create .abi-compliance-history file for v19
  2026-11-17 16:42 create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
  2026-11-17 22:39 ` Re: create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
  2026-11-18 02:22   ` Re: create .abi-compliance-history file for v19 Andrew Dunstan <andrew@dunslane.net>
@ 2026-11-18 02:24     ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2026-11-18 02:24 UTC (permalink / raw)
  To: Andrew Dunstan <andrew@dunslane.net>; +Cc: Nathan Bossart <nathandbossart@gmail.com>; pgsql-hackers

Andrew Dunstan <andrew@dunslane.net> writes:
> Should this be added to release procedures?

It's mentioned in RELEASE_CHANGES, although perhaps not very
prominently.  We don't have a separate section there for
post-major-release steps.

			regards, tom lane






^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2026-11-18 02:24 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-11-17 16:42 create .abi-compliance-history file for v19 Nathan Bossart <nathandbossart@gmail.com>
2026-11-17 22:39 ` Nathan Bossart <nathandbossart@gmail.com>
2026-11-18 02:22   ` Andrew Dunstan <andrew@dunslane.net>
2026-11-18 02:24     ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox