| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: First-draft back-branch release notes are up |
| Date: | 2025-05-04 03:55:37 |
| Message-ID: | 2263186.1746330937@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
jian he <jian(dot)universality(at)gmail(dot)com> writes:
> we have two commits,
> https://git.postgresql.org/cgit/postgresql.git/commit/?id=d6dd2a02bae0d67ff6fbd73068dc36d0b82fc14b
> and
> https://git.postgresql.org/cgit/postgresql.git/commit/?id=bd178960c69bae972c274af8102da9018df8196a
> we should include both commit's authors...
Argh --- yes, I missed you in crediting that one. My apologies,
will fix tomorrow.
> BTW, I found that for minor releases, bug reporter is not included....
No, we generally haven't done that in release notes, only in the
commit log. I think the only cases where we credit reporters in
the release notes are CVE-worthy security bugs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-05-04 05:02:51 | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Previous Message | jian he | 2025-05-04 03:20:42 | Re: First-draft back-branch release notes are up |