Re: PG 18 beta1 release notes misses mention of pg_noreturn

On Mon, Jul 28, 2025 at 03:06:23PM +0200, Daniel Gustafsson wrote:
> > On 25 Jul 2025, at 00:22, Bruce Momjian <bruce@momjian.us> wrote:
> > 
> > On Wed, Jul  2, 2025 at 06:23:52PM +0200, Daniel Gustafsson wrote:
> >>> On 2 Jul 2025, at 04:51, Steve Chavez <steve@supabase.io> wrote:
> >> 
> >>> While updating an extension to support 18beta1, I stumbled on the removal of `pg_attribute_noreturn()` in favor
of`pg_noreturn`, which wasn't mentioned in the release notes.
 
> >> 
> >> That admittedly seems like something worth including since it's otherwise not
> >> documented anywhere.
> > 
> > I don't add changes to the release notes that would only affect
> > extension authors because there are many such changes, and such changes
> > would be meaningless to non-extension authors.  If we want to document
> > this, we would need an extension-author specific release notes list.
> 
> I totally agree that the release notes cannot contain all changes, and lot's of
> important changes must be left out to make them manageable (the proposed change
> here might well be one such change), but a blanket no for extension authors
> seem counterproductive given how valuable they are to our ecosystem.  A "what
> would you like from the documentation" session at the next extension author
> summit would be probably be interesting for getting insights into what is
> missing and what could be improved.

There is no clear boundry on what extension authors should see in the
main release notes vs. seeing all changes that affect extensions, so I
have never tried to include them.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.