Out-of-cycle release on 2025-02-20

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Out-of-cycle release on 2025-02-20
Date: 2025-02-14 02:08:21
Message-ID: 272abbd9-d24c-49f1-8b61-83721906aa3b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

CVE-2025-1094[1] introduced a regression that was reported fairly
shortly after the release[2]. Based on the nature of the report and the
fact it's in libpq, the release team was unsure of what the overall
prevalence of the issue given its client-facing, and decided to have an
out-of-cycle release on 2025-02-20[3] to handle this sooner than the
regularly scheduled release[4].

Per standard release process, any patches being committed for this
release must be in by 2025-02-15 12:00 UTC to ensure they have ample
time to get through the buildfarm.

Thanks,

Jonathan

[1] https://www.postgresql.org/support/security/CVE-2025-1094/
[2] https://www.postgresql.org/message-id/Z64jD3u46gObCo1p%40pryzbyj2023
[3]
https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-20-2025-3016/
[4] https://www.postgresql.org/developer/roadmap/

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2025-02-14 04:16:06 Re: Parallel heap vacuum
Previous Message Melanie Plageman 2025-02-14 02:06:16 Re: Confine vacuum skip logic to lazy_scan_skip