Re: PG 16 draft release notes ready

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 16 draft release notes ready
Date: 2023-05-21 00:35:39
Message-ID: ZGlnW3CCQHV3cdZ3@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 19, 2023 at 11:08:18PM -0400, Isaac Morland wrote:
> On Fri, 19 May 2023 at 22:59, jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
>
> Sorry for changing the subject line..... 
>
> these two commits seems not mentioned.
>
>
> On a similar topic, should every committed item from the commitfest be
> mentioned, or only ones that are significant enough?
>
> I’m wondering because I had a role in this very small item, yet I don’t see it
> listed in the psql section:
>
> https://commitfest.postgresql.org/42/4133/
>
> It’s OK if we don’t mention every single change, I just want to make sure I
> understand.

I have never considered the presence of an item in the commitfest as an
indicator of importance to be in the release notes. The major release
notes, for me, is a balance of listing the most visible changes without
going into unmanageable detail.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-05-21 00:51:21 Re: PG 16 draft release notes ready
Previous Message Bruce Momjian 2023-05-21 00:32:36 Re: PG 16 draft release notes ready