@@ -50,30 +50,37 @@ <h2>Latest Releases</h2>
5050 < div class ="text ">
5151 < p >
5252 < strong >
53- 2024-05-09 -
54- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219- released-2858 / ">
55- PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19 Released!
53+ 2024-05-23 -
54+ < a href ="/about/news/postgresql-17-beta-1- released-2865 / ">
55+ PostgreSQL 17 Beta 1 Released!
5656 </ a >
5757 </ strong >
5858 </ p >
5959 < p >
60- The PostgreSQL Global Development Group has
61- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219-released-2858/ "> released an update</ a >
62- to all supported versions of PostgreSQL, including
63- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219-released-2858/ "> 16.3, 15.7, 14.12, 13.15, and 12.19</ a > .
64- This release fixes one < a href ="/support/security/ "> security vulnerability</ a >
65- and over 55 bugs reported over the last several months.
60+ The PostgreSQL Global Development Group announces that the first
61+ beta release of PostgreSQL 17 is now < a href ="/download/ "> available for download</ a > .
62+ This release contains previews of all features that will be available
63+ when PostgreSQL 17 is made generally available, though some details of
64+ the release can change during the beta period.
6665 </ p >
6766 < p >
68- Please note that the fix in this release for
69- < a href ="/support/security/CVE-2024-4317/ "> CVE-2024-4317</ a >
70- only fixes fresh PostgreSQL installations, namely those that are
71- created with the < a href ="/docs/current/app-initdb.html "> < code > initdb</ code > </ a >
72- utility after this fix is applied. If you have a current PostgreSQL
73- installation and are concerned about this issue, please follow the
74- additional updating instructions provided in the
75- < a href ="/support/security/CVE-2024-4317/ "> CVE-2024-4317</ a > description
76- or the < a href ="/docs/release/ "> release notes</ a > for the remediation.
67+ You can find information about all of the PostgreSQL 17 features and
68+ changes in the < a href ="/docs/17/release-17.html "> release notes</ a > .
69+ </ p >
70+ < p >
71+ In the spirit of the open source PostgreSQL community, we strongly
72+ encourage you to test the new features of PostgreSQL 17 on your
73+ systems to help us eliminate bugs or other issues that may exist.
74+ While we do not advise you to run PostgreSQL 17 Beta 1 in production
75+ environments, we encourage you to find ways to run your typical
76+ application workloads against this beta release.
77+ </ p >
78+ < p >
79+ Your testing and feedback will help the community ensure that the
80+ PostgreSQL 17 release upholds our standards of delivering a stable,
81+ reliable release of the world's most advanced open source relational
82+ database. Please read more about our < a href ="/developer/beta/ "> beta testing process</ a >
83+ and how you can contribute.
7784 </ p >
7885 < p >
7986 PostgreSQL 12 will < a href ="/support/versioning/ "> </ a > stop receiving fixes</ a >
@@ -83,11 +90,6 @@ <h2>Latest Releases</h2>
8390 < a href ="/support/versioning/ "> </ a > versioning policy</ a > for more
8491 information.
8592 </ p >
86- < p >
87- For the more information about this release, please review the
88- < a href ="/docs/release/ "> release notes</ a > . You can download
89- PostgreSQL from the < a href ="/download/ "> download</ a > page.
90- </ p >
9193 < ul >
9294 {% for v in versions %}
9395 < li class ="{% cycle '' 'pg-bg-gray' %} "> < strong > {{ v.numtree }}.{{ v.latestminor }}</ strong > · {{ v.reldate|date:"Y-m-d" }} · < a href ="/docs/{{ v.numtree }}/{{ v.relnotes }} "> Notes</ a > </ li >
@@ -170,46 +172,45 @@ <h2 class="centered-lines">Latest News</h2>
170172 <!-- Featured Post -->
171173 < header >
172174 < h3 >
173- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219- released-2858 / ">
174- PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19 Released!
175+ < a href ="/about/news/postgresql-17-beta-1- released-2865 / ">
176+ PostgreSQL 17 Beta 1 Released!
175177 </ a >
176178 </ h3 >
177179 < ul class ="meta ">
178- < li > < i class ="far fa-clock "> </ i > 2024-05-09 </ li >
180+ < li > < i class ="far fa-clock "> </ i > 2024-05-23 </ li >
179181 <!--<li><i class="far fa-comments"></i> 0</li>-->
180182 </ ul >
181183 </ header >
182184 < p >
183- The PostgreSQL Global Development Group has
184- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219-released-2858/ "> released an update</ a >
185- to all supported versions of PostgreSQL, including
186- < a href ="/about/news/postgresql-163-157-1412-1315-and-1219-released-2858/ "> 16.3, 15.7, 14.12, 13.15, and 12.19</ a > .
187- This release fixes one < a href ="/support/security/ "> security vulnerability</ a >
188- and over 55 bugs reported over the last several months.
185+ The PostgreSQL Global Development Group announces that the first
186+ beta release of PostgreSQL 17 is now < a href ="/download/ "> available for download</ a > .
187+ This release contains previews of all features that will be available
188+ when PostgreSQL 17 is made generally available, though some details of
189+ the release can change during the beta period.
189190 </ p >
190191 < p >
191- Please note that the fix in this release for
192- < a href ="/support/security/CVE-2024-4317/ "> CVE-2024-4317</ a >
193- only fixes fresh PostgreSQL installations, namely those that are
194- created with the < a href ="/docs/current/app-initdb.html "> < code > initdb</ code > </ a >
195- utility after this fix is applied. If you have a current PostgreSQL
196- installation and are concerned about this issue, please follow the
197- additional updating instructions provided in the
198- < a href ="/support/security/CVE-2024-4317/ "> CVE-2024-4317</ a > description
199- or the < a href ="/docs/release/ "> release notes</ a > for the remediation.
192+ You can find information about all of the PostgreSQL 17 features and
193+ changes in the < a href ="/docs/17/release-17.html "> release notes</ a > .
200194 </ p >
201195 < p >
202- PostgreSQL 12 will < a href ="/support/versioning/ "> </ a > stop receiving fixes</ a >
203- on November 14, 2024. If you are running PostgreSQL 12 in a
204- production environment, we suggest that you make plans to upgrade to a
205- newer, supported version of PostgreSQL. Please see our
206- < a href ="/support/versioning/ "> </ a > versioning policy</ a > for more
207- information.
196+ In the spirit of the open source PostgreSQL community, we strongly
197+ encourage you to test the new features of PostgreSQL 17 on your
198+ systems to help us eliminate bugs or other issues that may exist.
199+ While we do not advise you to run PostgreSQL 17 Beta 1 in production
200+ environments, we encourage you to find ways to run your typical
201+ application workloads against this beta release.
202+ </ p >
203+ < p >
204+ Your testing and feedback will help the community ensure that the
205+ PostgreSQL 17 release upholds our standards of delivering a stable,
206+ reliable release of the world's most advanced open source relational
207+ database. Please read more about our < a href ="/developer/beta/ "> beta testing process</ a >
208+ and how you can contribute.
208209 </ p >
209210 < ul class ="bold ">
210- < li > < a href ="/about/news/postgresql-163-157-1412-1315-and-1219- released-2858 / "> Release Announcement</ a > </ li >
211- < li > < a href ="/docs/release/ "> Release Notes</ a > </ li >
212- < li > < a href ="/about/press / "> PostgreSQL 16 Release Announcement & Translations </ a > </ li >
211+ < li > < a href ="/about/news/postgresql-17-beta-1- released-2865 / "> Release Announcement</ a > </ li >
212+ < li > < a href ="/docs/17/release-17.html "> Release Notes</ a > </ li >
213+ < li > < a href ="/developer/beta / "> Beta Testing Information </ a > </ li >
213214 < li > < a href ="/support/versioning/ "> Versioning Policy</ a > </ li >
214215 < li > < a href ="/download/ "> Download</ a > </ li >
215216 </ ul >
0 commit comments