| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 15 GA release date |
| Date: | 2022-10-03 12:40:13 |
| Message-ID: | 20221003124013.mpurwuotkep7ni3r@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 03, 2022 at 09:05:34AM -0300, Ranier Vilela wrote:
> >Please let us know if you have any questions. We're excited that we are
> >very close to officially releasing PostgreSQL 15.
> Hi, forgive my ignorance.
> What are the rules for a commit to be included in the release notes?
> Does it need to be explicitly requested?
>
> Why is the commit 8cb2a22
> <https://github.com/postgres/postgres/commit/8cb2a22bbb2cf4212482ac15021ceaa2e9c52209>
> (bug fix), not included?
> I think users of this function should be better informed.
That commit has been backpatched, so it's not new in pg15 and will be in the
release notes of the next minor versions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume de Rorthais | 2022-10-03 12:47:57 | Re: [BUG] parenting a PK constraint to a self-FK one (Was: Self FK oddity when attaching a partition) |
| Previous Message | Justin Pryzby | 2022-10-03 12:39:40 | Re: PostgreSQL 15 GA release date |