[SCM] PostGIS branch stable-3.6 updated. 3.6.0rc2-5-ga8849da69
git at osgeo.org
git at osgeo.org
Sun Aug 31 22:14:21 PDT 2025
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".
The branch, stable-3.6 has been updated
via a8849da695ff6380003c72f15114285ed662ba96 (commit)
from dc8aa04a910c81e4ea86c44e9cd97a8bbb6a616c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a8849da695ff6380003c72f15114285ed662ba96
Author: Regina Obe <lr at pcorp.us>
Date: Mon Sep 1 01:13:59 2025 -0400
Prep for 3.6.0 release
diff --git a/NEWS b/NEWS
index d120be655..7435a37ec 100644
--- a/NEWS
+++ b/NEWS
@@ -1,27 +1,5 @@
-PostGIS 3.6.0rc2
-2025/08/25
-This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
-To take advantage of all features, GEOS 3.14+ is needed.
-To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed.
-
-Many thanks to our translation teams, in particular:
-
-Teramoto Ikuhiro (Japanese Team)
-Daniel Nylander (Swedish Team)
-Dapeng Wang, Zuo Chenwei from HighGo (Chinese Team)
-Denys Kovshun (Ukrainian Team)
-
-CHANGES since PostGIS 3.6.0rc1
-
- - #5977, Fix downgrade protection with standard conforming strings off (Sandro Santilli)
- - Doc updates
- - #5968, Remove raster generated files in distclean target (Bas Couwenberg)
- - #5969, Fix issue when building --without-topology (Regina Obe)
- - #5971, Option to build --without-tiger (Regina Obe)
-
-
PostGIS 3.6.0
-2025/xx/xx
+2025/09/01
This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
To take advantage of all features, GEOS 3.14+ is needed.
@@ -76,4 +54,26 @@ Denys Kovshun (Ukrainian Team)
- #3110, GT-242 [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)
- [raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)
- #5963, [raster] add ST_IntersectionFractions - Requires GEOS 3.14 (Paul Ramsey)
+ - #5971, Option to build --without-tiger (Regina Obe)
+
+PostGIS 3.6.0rc2
+2025/08/25
+This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
+To take advantage of all features, GEOS 3.14+ is needed.
+To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed.
+
+Many thanks to our translation teams, in particular:
+
+Teramoto Ikuhiro (Japanese Team)
+Daniel Nylander (Swedish Team)
+Dapeng Wang, Zuo Chenwei from HighGo (Chinese Team)
+Denys Kovshun (Ukrainian Team)
+
+CHANGES since PostGIS 3.6.0rc1
+
+ - #5977, Fix downgrade protection with standard conforming strings off (Sandro Santilli)
+ - Doc updates
+ - #5968, Remove raster generated files in distclean target (Bas Couwenberg)
+ - #5969, Fix issue when building --without-topology (Regina Obe)
+ - #5971, Option to build --without-tiger (Regina Obe)
diff --git a/README.postgis b/README.postgis
index 65494b7a9..009525190 100644
--- a/README.postgis
+++ b/README.postgis
@@ -1,8 +1,8 @@
PostGIS - Geographic Information Systems Extensions to PostgreSQL
=================================================================
-:Version: 3.6.0rc2
-:Date: 2025-08-25
+:Version: 3.6.0
+:Date: 2025-09-01
:Website: https://postgis.net
This distribution contains a module which implements GIS simple features, ties
diff --git a/Version.config b/Version.config
index cf6d63e9f..272078014 100644
--- a/Version.config
+++ b/Version.config
@@ -5,7 +5,7 @@
POSTGIS_MAJOR_VERSION=3
POSTGIS_MINOR_VERSION=6
-POSTGIS_MICRO_VERSION=0dev
+POSTGIS_MICRO_VERSION=0
# Liblwgeom interface versioning, reset to 0:0:0 (cur:age:rev)
# when changing POSTGIS_MINOR_VERSION
diff --git a/doc/developer.md b/doc/developer.md
index c83302e9e..3c51f4cab 100644
--- a/doc/developer.md
+++ b/doc/developer.md
@@ -42,8 +42,8 @@ The libraries of these were always separate, however the name rtpostgis- that pa
name so was renamed, but for all purposes rtpostgis of the past is equivalent to postgis_raster of the present.
All these changes were made to ease upgrade pains with pg_upgrade.
-As a developer you still have the option of having your lib files minor versioned
-for easier testing in the same cluster.
+As a developer you still have the option of having your lib files minor versioned
+for easier testing in the same cluster.
To take advantage of this feature, when configuring postgis compile, use the switch *--with-library-minor-version*
@@ -58,7 +58,7 @@ To take advantage of this feature, when configuring postgis compile, use the swi
* Only major versions can remove SQL api functions
or C api functions without stubbing (which we will cover shortly).
-* Only PostGIS first release of a major can introduce functionality that requires a pg_dump / pg_restore.
+* Only PostGIS first release of a major can introduce functionality that requires a pg_dump / pg_restore.
* Don't require newer versions of library in a micro, but you can require new versions in first release of a minor.
For example we often drop support for older versions of GEOS and PostgreSQL in a new minor release.
@@ -72,55 +72,55 @@ There are several types of removals that impact user upgrades and should be care
* C Api functions
* Types, Views, Tables are also exposed via SQL Api
-Functions internal to postgis that are never exposed and only used within postgis libraries
+Functions internal to postgis that are never exposed and only used within postgis libraries
can be shuffled around to your hearts content.
-## UPGRADING C Api functions
+## UPGRADING C Api functions
You should avoid ever removing C Api function in Minor and patch releases of PostGIS.
-If there is a C Api function that you badly want to remove you need to stub it so the signature still
+If there is a C Api function that you badly want to remove you need to stub it so the signature still
exists but throws an error.
-These functions should be removed from whatever file
+These functions should be removed from whatever file
they were in and stubbed in a deprecation file. Ideally you should never do this in a micro. Only minor.
For Major such as when PostGIS 4 comes out we could in theory skip the legacy file and just chuck the function entirely.
We could even blank out all the legacy files.
-A function can be stubbed in 3.0.0, but not 3.0.1, though there are cases where you might as long as
-you carefully fix up the SQL signature exposing it. The reason to avoid not doing this in a micro is people often do not
+A function can be stubbed in 3.0.0, but not 3.0.1, though there are cases where you might as long as
+you carefully fix up the SQL signature exposing it. The reason to avoid not doing this in a micro is people often do not
run ALTER EXTENSION or SELECT postgis_extensions_upgrade() in a micro, so taking these out will break production code.
- * For the postgis extension, these should go in postgis/postgis_legacy.c the stub will look something like this.
+ * For the postgis extension, these should go in postgis/postgis_legacy.c the stub will look something like this.
POSTGIS_DEPRECATE("2.0.0", postgis_uses_stats)
Note the specification of the version it was removed and the name of the function
- * For postgis_sfcgal, deprecated C api functions should go in sfcgal/postgis_sfcgal_legacy.c
+ * For postgis_sfcgal, deprecated C api functions should go in sfcgal/postgis_sfcgal_legacy.c
* For postgis_raster, raster/rt_pg/rtpg_legacy.c
* postgis_topology extension has never had any deprecated functions so there is currently no legacy file for it.
If there comes a need to deprecate C functions, then a file topology/postgis_topology_legacy.c will be created to store these.
- * postgis_tiger_geocoder is all sql and plpgsql so it has no C backing functions.
+ * postgis_tiger_geocoder is all sql and plpgsql so it has no C backing functions.
-Why do we even bother replacing a good function with a function that throws an error? Because of pg_upgrade tool used
-to upgrade PostgreSQL clusters. When pg_upgrade runs, it does not use the regular CREATE EXTENSION routine that loads function definitions from
+Why do we even bother replacing a good function with a function that throws an error? Because of pg_upgrade tool used
+to upgrade PostgreSQL clusters. When pg_upgrade runs, it does not use the regular CREATE EXTENSION routine that loads function definitions from
a file. Instead it uses a naked CREATE EXTENSION and then tries to load all functions /types /etc/ from the old databases as they existed
-meaning they point at the same .so, .dll, .dylib whatever. When it tries to load these in, it validates the library to make sure said
-functions exist in the library. If these functions don't it will bail and pg_upgrade will fail. It however will do fine
+meaning they point at the same .so, .dll, .dylib whatever. When it tries to load these in, it validates the library to make sure said
+functions exist in the library. If these functions don't it will bail and pg_upgrade will fail. It however will do fine
not complain if the function exists even if all the function knows how to do is throw an error.
WHY oh WHY does it use old signatures in an old database instead of a fresh CREATE EXTENSION install?
-Primarily because objects are referenced by object identifiers AKA oids in views, tables, you name it, and if you create new function
+Primarily because objects are referenced by object identifiers AKA oids in views, tables, you name it, and if you create new function
from scratch, even if it has the same exact definition as the old, it does not have the same OID.
-As such all db internal references would be broken
+As such all db internal references would be broken
if you try to overlay the old def structures onto the new extension install.
So this whole care of legacy functions is to appease pg_upgrade.
-## UPGRADING SQL Api functions
+## UPGRADING SQL Api functions
For most SQL Api functions, nothing special needs to be done beyond
noting a CHANGED in version or AVAILABILITY in the respective .sql.in files.
@@ -134,7 +134,7 @@ The SQL Api definitions are found in following places:
| `postgis_sfcgal` | `sfcgal/sfcgal_sql.in` |
| `postgis_topology` | `topology/sql/*.sql.in` |
-We use perl scripts to stitch together these various SQL and
+We use perl scripts to stitch together these various SQL and
read meta comments to determine what to do during an upgrade.
The utils/create_upgrade.pl is the script that is tasked with creating upgrade scripts.
@@ -142,13 +142,13 @@ The various notes you put in .sql.in files take the following form and precede t
* -- Availability: Is only informational 2.0.0 where 2.0.0 represents the version it was introduced in.
* -- Changed: Is only informational. You'll often see an Availability comment followed by a changed comment.
- e.g.
+ e.g.
-- Availability: 0.1.0
-- Changed: 2.0.0 use gserialized selectivity estimators
-
+
* -- Replaces: is both informational and also instructs the perl upgrade script to protect the user from some upgrade pains.
- You use Replaces instead of just a simple Changed, if you are changing inputs to the function or changing
+ You use Replaces instead of just a simple Changed, if you are changing inputs to the function or changing
outputs of the function. So any change to the api
Such a comment would look something like:
@@ -160,13 +160,13 @@ The various notes you put in .sql.in files take the following form and precede t
When utils/create_upgrade.pl script comes across a Replaces clause, the perl script will change the statement to do the following:
1) Finds the old definition
- 2) renames the old definition to ST_Force3D_deprecated_by_postgis_310
+ 2) renames the old definition to ST_Force3D_deprecated_by_postgis_310
3) Installs the new version of the function.
- 4) At the end of the upgrade script, it will try to drop the function. If the old function is bound
- to user objects, it will leave the old function alone and warn the user as part of the upgrade, that they have objects bound to an old signature.
+ 4) At the end of the upgrade script, it will try to drop the function. If the old function is bound
+ to user objects, it will leave the old function alone and warn the user as part of the upgrade, that they have objects bound to an old signature.
- Why do we do this? Because all objects are bound by oids and not names. So if a user has a view or materialized view, it will be bound to
- ST_Force3D_deprecated_by_postgis_310 and not the new ST_Force3D. We can't drop things bound to user objects without executing a
+ Why do we do this? Because all objects are bound by oids and not names. So if a user has a view or materialized view, it will be bound to
+ ST_Force3D_deprecated_by_postgis_310 and not the new ST_Force3D. We can't drop things bound to user objects without executing a
DROP ... CASCADE, which will destroy user objects.
@@ -179,12 +179,12 @@ If you need something dropped or need to make some system changes that would pre
The relevant files for each extension are as follows:
* postgis - postgis/postgis_before_upgrade.sql , postgis/postgis_after_upgrade.sql
-* postgis_raster - raster/rtpostgis_drop.sql.in, rtpostgis_upgrade_cleanup.sql.in
+* postgis_raster - raster/rtpostgis_drop.sql.in, rtpostgis_upgrade_cleanup.sql.in
(the rtpostgis_upgrade_cleanup.sql.in is equivalent to the after_upgrade script of other extensions)
* postgis_sfcgal - sfcgal/sfcgal_before_upgrade.sql.in, sfcgal/sfcgal_after_upgrade.sql.in
* postgis_topology - topology/topology_before_upgrade.sql.in, topology/topology_after_upgrade.sql.in
-Helper function calls you'll find in these scripts are the following and are defined in postgis/common_before_upgrade.sql and dropped in
+Helper function calls you'll find in these scripts are the following and are defined in postgis/common_before_upgrade.sql and dropped in
postgis/common_after_upgrade.sql
* _postgis_drop_function_by_signature - generally you want to use this one as it only cares about input types of functions
@@ -210,7 +210,7 @@ We have guards in place in the code to handle these for dependency libraries
* PostgreSQL
- sql.in and c files
-
+
```c
#if POSTGIS_PGSQL_VERSION >= 150
/* code that requires PostgreSQL 15+ */
@@ -219,15 +219,15 @@ We have guards in place in the code to handle these for dependency libraries
- regress/../tests.mk.in
-* GEOS
- - c:
+* GEOS
+ - c:
```c
#if POSTGIS_GEOS_VERSION < 31000
/* GEOS < 3.1 code goes here */
#endif
```
- test files:
- * **`regress/**/tests.mk.in`**
+ * **`regress/**/tests.mk.in`**
* raster/rt_pg/tests/tests.mi.in
```makefile
@@ -244,7 +244,7 @@ We have guards in place in the code to handle these for dependency libraries
/* SFCGAL 2.1+ required */
#endif
```
- - tests:
+ - tests:
* sfcgal/regress/tests.mk.in
```makefile
@@ -262,12 +262,12 @@ We have guards in place in the code to handle these for dependency libraries
```
* GDAL
- - c files
+ - c files
```c
#if POSTGIS_GDAL_VERSION < 30700
/* Logic for GDAL < 3.7 **/
#endif
- ```
+ ```
Even if a user can't use a certain function, that function still needs to be exposed,
but instead of doing something functional, will output an error that the extension needs to be compiled
diff --git a/doc/po/ja/postgis-manual.po b/doc/po/ja/postgis-manual.po
index ce5137d17..49c822b0d 100644
--- a/doc/po/ja/postgis-manual.po
+++ b/doc/po/ja/postgis-manual.po
@@ -10,7 +10,7 @@ msgstr ""
"Project-Id-Version: postgis 3.5\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
"POT-Creation-Date: 2025-08-21 03:28+0000\n"
-"PO-Revision-Date: 2025-08-22 10:47+0000\n"
+"PO-Revision-Date: 2025-08-25 08:47+0000\n"
"Last-Translator: Teramoto Ikuhiro <teramoto.ikuhiro576 at naro.go.jp>\n"
"Language-Team: Japanese <https://weblate.osgeo.org/projects/postgis/postgis-"
"manual/ja/>\n"
@@ -8572,12 +8572,12 @@ msgstr "ラスタ機能なしでコンパイルします。"
#. Tag: para
#, no-c-format
msgid "Disables tiger geocoder support."
-msgstr ""
+msgstr "Tigerジオコーダー機能を無効にします。"
#. Tag: para
#, no-c-format
msgid "Compile without topology support."
-msgstr ""
+msgstr "トポロジー機能なしでコンパイルします。"
#. Tag: para
#, no-c-format
@@ -43775,12 +43775,12 @@ msgstr "リリースノート"
#. Tag: title
#, no-c-format
msgid "PostGIS 3.6.0rc2"
-msgstr ""
+msgstr "PostGIS 3.6.0rc2"
#. Tag: para
#, no-c-format
msgid "2025/08/25"
-msgstr ""
+msgstr "2025/08/25"
#. Tag: para
#, no-c-format
diff --git a/doc/po/sv/postgis-manual.po b/doc/po/sv/postgis-manual.po
index 8f9b908a7..700003839 100644
--- a/doc/po/sv/postgis-manual.po
+++ b/doc/po/sv/postgis-manual.po
@@ -5,7 +5,7 @@ msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
"POT-Creation-Date: 2025-08-21 03:28+0000\n"
-"PO-Revision-Date: 2025-07-20 08:47+0000\n"
+"PO-Revision-Date: 2025-08-25 19:47+0000\n"
"Last-Translator: Daniel Nylander <daniel at danielnylander.se>\n"
"Language-Team: Swedish <https://weblate.osgeo.org/projects/postgis/postgis-"
"manual/sv/>\n"
@@ -8756,12 +8756,12 @@ msgstr "Kompilera utan stöd för raster."
#. Tag: para
#, no-c-format
msgid "Disables tiger geocoder support."
-msgstr ""
+msgstr "Inaktiverar stöd för tiger geocoder."
#. Tag: para
#, no-c-format
msgid "Compile without topology support."
-msgstr ""
+msgstr "Kompilera utan topologistöd."
#. Tag: para
#, no-c-format
@@ -10574,7 +10574,7 @@ msgstr "David Techer"
#. Tag: member
#, no-c-format
msgid "Denys Kovshun"
-msgstr ""
+msgstr "Denys Kovshun"
#. Tag: member
#, no-c-format
@@ -37917,7 +37917,7 @@ msgstr ""
msgid ""
"Calculates the fraction of each raster cell that is covered by a given "
"geometry."
-msgstr ""
+msgstr "Beräknar den del av varje rastercell som täcks av en given geometri."
#. Tag: para
#, no-c-format
@@ -37931,11 +37931,19 @@ msgid ""
"that is covered by the geometry. For linestrings, the value returned for "
"each cell is the length contained in the cell."
msgstr ""
+"Beräknar den del av varje rastercell som täcks av en given geometri. Det "
+"första argumentet är en raster som definierar rutnätets geometri som ska "
+"användas för beräkningen. Omfattningen och cellstorleken läses från "
+"rasterparametern. Det andra argumentet är en geometri som läggs över "
+"rutnätet, och varje rutnät fylls i baserat på överlagringen av geometrin på "
+"rutnätet. För polygoner är det värde som returneras för varje cell andelen "
+"av dess area som täcks av geometrin. För linjesträngar är det värde som "
+"returneras för varje cell längden som ingår i cellen."
#. Tag: para
#, no-c-format
msgid "Availability: 3.6.0 Requires GEOS 3.14 or higher."
-msgstr ""
+msgstr "Tillgänglighet: 3.6.0 Kräver GEOS 3.14 eller högre."
#. Tag: title
#, no-c-format
@@ -45001,12 +45009,12 @@ msgstr "Anteckningar för release"
#. Tag: title
#, no-c-format
msgid "PostGIS 3.6.0rc2"
-msgstr ""
+msgstr "PostGIS 3.6.0rc2"
#. Tag: para
#, no-c-format
msgid "2025/08/25"
-msgstr ""
+msgstr "2025-08-25"
#. Tag: para
#, no-c-format
@@ -45015,6 +45023,9 @@ msgid ""
"6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take "
"advantage of all SFCGAL features, SFCGAL 2.2+ is needed."
msgstr ""
+"Denna version kräver PostgreSQL 12-18beta3, GEOS 3.8 eller högre och Proj "
+"6.1+. För att kunna utnyttja alla funktioner krävs GEOS 3.14+. För att kunna "
+"utnyttja alla SFCGAL-funktioner krävs SFCGAL 2.2+."
#. Tag: para
#, no-c-format
@@ -45039,7 +45050,7 @@ msgstr "Dapeng Wang, Zuo Chenwei från HighGo (kinesiska teamet)"
#. Tag: para
#, no-c-format
msgid "Denys Kovshun (Ukrainian Team)"
-msgstr ""
+msgstr "Denys Kovshun (Ukrainska teamet)"
#. Tag: title
#, no-c-format
@@ -45115,6 +45126,12 @@ msgid ""
"extension@ for PG >= 16 to schema qualify dependent extensions, switch to "
"use typmod for tiger tables (Regina Obe)"
msgstr ""
+"<link xlink:href=\"https://trac.osgeo.org/postgis/ticket/5359\">#5359</"
+"link>, <link xlink:href=\"https://trac.osgeo.org/postgis/"
+"ticket/5897\">#5897</link>, <link xlink:href=\"https://git.osgeo.org/gitea/"
+"postgis/postgis/pulls/260\">GT-260</link> [tiger_geocoder] Använd @extschema:"
+"extension@ för PG >= 16 för att schema-kvalificera beroende tillägg, byt "
+"till typmod för tiger-tabeller (Regina Obe)"
#. Tag: title
#, no-c-format
@@ -45128,6 +45145,10 @@ msgid ""
"Drop st_approxquantile(raster, double precision), wasn't usable as it "
"triggered is not unique error when used (Regina Obe)"
msgstr ""
+"<link xlink:href=\"https://trac.osgeo.org/postgis/ticket/5498\">#5498</link> "
+"Ta bort st_approxquantile(raster, double precision), kunde inte användas "
+"eftersom det utlöste ett felmeddelande om att det inte var unikt när det "
+"användes (Regina Obe)"
#. Tag: title
#, no-c-format
@@ -45275,6 +45296,8 @@ msgstr ""
msgid ""
"[raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)"
msgstr ""
+"[raster] Lägg till ST_ReclassExact för att snabbt ommappa värden i raster "
+"(Paul Ramsey)"
#. Tag: title
#, no-c-format
diff --git a/doc/po/uk/postgis-manual.po b/doc/po/uk/postgis-manual.po
index 13d3d4be6..196c2131c 100644
--- a/doc/po/uk/postgis-manual.po
+++ b/doc/po/uk/postgis-manual.po
@@ -6,7 +6,7 @@ msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
"POT-Creation-Date: 2025-07-20 04:11+0000\n"
-"PO-Revision-Date: 2025-08-20 21:47+0000\n"
+"PO-Revision-Date: 2025-08-31 21:47+0000\n"
"Last-Translator: Denys Kovshun <deniskovshun at gmail.com>\n"
"Language-Team: Ukrainian <https://weblate.osgeo.org/projects/postgis/"
"postgis-manual/uk/>\n"
@@ -27350,7 +27350,7 @@ msgstr "Вхідні лінії"
#. Tag: para
#, no-c-format
msgid "Area result"
-msgstr "Площа результату"
+msgstr "Результати за площею"
#. Tag: para
#, no-c-format
diff --git a/doc/postgis.xml b/doc/postgis.xml
index 77a4ead52..2e59a1cad 100644
--- a/doc/postgis.xml
+++ b/doc/postgis.xml
@@ -5,14 +5,14 @@
<!-- This value is automatically generated by the Makefile -->
<!ENTITY last_release_version "@@LAST_RELEASE_VERSION@@">
-<!ENTITY last_minor_version "3.4">
+<!ENTITY last_minor_version "3.5">
<!-- ONCE Tagged, this need to change to http://download.osgeo.org/postgis/source/postgis-@@LAST_RELEASE_VERSION@@.tar.gz -->
<!-- In dev should be, this need to change to http://postgis.net/stuff/postgis-@@LAST_RELEASE_VERSION@@.tar.gz -->
<!ENTITY postgis_download_url "@@POSTGIS_DOWNLOAD_URL@@/postgis-@@LAST_RELEASE_VERSION@@.tar.gz">
<!-- Change these values to update the version numbers referenced within the documentation -->
-<!ENTITY last_proj_release_version "9.2.1">
+<!ENTITY last_proj_release_version "9.6.1">
<!ENTITY last_geos_release_version "3.14.0">
<!ENTITY min_geos_version "3.8.0">
<!ENTITY min_postgres_version "12">
diff --git a/doc/release_notes.xml b/doc/release_notes.xml
index 9fa7182f7..f750b9637 100644
--- a/doc/release_notes.xml
+++ b/doc/release_notes.xml
@@ -3,8 +3,8 @@
<title>Appendix</title>
<subtitle>Release Notes</subtitle>
<section>
- <title>PostGIS 3.6.0rc2</title>
- <para>2025/08/25</para>
+ <title>PostGIS 3.6.0</title>
+ <para>2025/09/01</para>
<para>This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
To take advantage of all features, GEOS 3.14+ is needed.
To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed.</para>
@@ -53,7 +53,7 @@
coverages (Paul Ramsey) from GEOS 3.14 (Martin Davis)</para>
<para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link> [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
<para>[raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)</para>
- <para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link>, [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
+ <para><link xlink:href="https://trac.osgeo.org/postgis/ticket/5971">#5971</link>, [tiger] Option to build --without-tiger (Regina Obe)</para>
</simplesect>
</section>
</appendix>
-----------------------------------------------------------------------
Summary of changes:
NEWS | 46 ++++++++++++++--------------
README.postgis | 4 +--
Version.config | 2 +-
doc/developer.md | 74 ++++++++++++++++++++++-----------------------
doc/po/ja/postgis-manual.po | 10 +++---
doc/po/sv/postgis-manual.po | 41 +++++++++++++++++++------
doc/po/uk/postgis-manual.po | 4 +--
doc/postgis.xml | 4 +--
doc/release_notes.xml | 6 ++--
9 files changed, 107 insertions(+), 84 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list