Re: Inquiry on planned PostGIS releases and minor-ve rsion behavior (now–Feb 28)

--0000000000009e2c720648eb1104
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Regina,

*"and yes we most likely will do a micro release before February 28" *

Could you please let us know if there is a tentative date planned for this
micro release? Additionally, will this release include any changes to *GEOS=
*
or *PROJ*?

On Wed, Jan 21, 2026 at 2:09=E2=80=AFPM Regina Obe <[email protected]> wrote:

> Bharath,
>
>
>
> The best advice I can give is to look at the upcoming NEWS items
>
>
>
> https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEWS
>
>
>
> and yes we most likely will do a micro release before February 28
>
>
>
>
>
> *From:* Bharath Tadikonda <[email protected]>
> *Sent:* Wednesday, January 21, 2026 1:36 PM
> *To:* [email protected]
> *Subject:* Inquiry on planned PostGIS releases and minor-version behavior
> (now=E2=80=93Feb 28)
>
>
>
> Hello PostGIS Team,
>
> I=E2=80=99m a PostgreSQL Database Engineer managing production PostgreSQL=
/PostGIS
> workloads on AWS RDS/Aurora.
>
> We are planning a PostgreSQL *minor upgrade* (PostgreSQL 16.6 =E2=86=92 1=
6.11) in
> the near term. In our environment, past *PostGIS minor/patch releases*
> have occasionally caused operational issues due to changes in function
> behavior, even when PostgreSQL itself was a minor upgrade. Because AWS ma=
y
> bundle a newer PostGIS minor version along with a PostgreSQL minor upgrad=
e,
> we want to plan and execute testing and production rollout as close
> together as possible.
>
> To help us plan safely, I wanted to ask:
>
>    1. *Are there any planned PostGIS releases (minor or patch) between
>    now and February 28?*
>
>
>    - If yes, which versions are anticipated?
>       - If not, when is the next postgis version release anticipated?
>
>
>    2. *For PostGIS minor/patch releases (e.g., 3.6.x =E2=86=92 3.6.y):*
>
>
>    - Are changes strictly bug fixes, or can they include behavioral
>       changes to existing functions?
>       - Are there specific classes of functions (geometry processing,
>       topology, raster, etc.) where behavior changes are more likely?
>
>
>    3. *Release notes & compatibility guidance:*
>
>
>    - Is there a recommended way to identify *function-level behavior
>       changes* between minor versions (beyond high-level release notes)?
>       - Are there guarantees or best-practice guidance around backward
>       compatibility expectations for PostGIS patch releases?
>
>
>    4. *Operational best practices:*
>
>
>    - Do you recommend pinning PostGIS patch versions in production where
>       possible, or validating only specific functions we rely on most dur=
ing
>       upgrades?
>
> Any guidance you can share will help us reduce risk and plan upgrades mor=
e
> confidently.
>
> Thank you for your time and for all the work you do on PostGIS.
>
> Best regards,
> Bharath
> PostgreSQL Database Engineer
>

--0000000000009e2c720648eb1104
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Regina,</div><div><br></div><span style=3D"color:r=
gb(0,0,0)"><i>&quot;and yes we most likely will do a micro release before F=
ebruary 28&quot;=C2=A0</i></span><div><span style=3D"color:rgb(0,0,0)"><i><=
br></i></span></div><div><p>Could you please let us know if there is a tent=
ative date planned for this micro release? Additionally, will this release =
include any changes to <strong>GEOS</strong> or <strong>PROJ</strong>?</p><=
/div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D=
"ltr" class=3D"gmail_attr">On Wed, Jan 21, 2026 at 2:09=E2=80=AFPM Regina O=
be &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"msg246271095=
1653754678"><div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"><div c=
lass=3D"m_2462710951653754678WordSection1"><p class=3D"MsoNormal">Bharath,<=
u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D=
"MsoNormal">The best advice I can give is to look at the upcoming NEWS item=
s<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=
=3D"MsoNormal"><a href=3D"https://gitea.osgeo.org/postgis/postgis/src/branc=
h/stable-3.6/NEWS" target=3D"_blank">https://gitea.osgeo.org/postgis/postgi=
s/src/branch/stable-3.6/NEWS</a><u></u><u></u></p><p class=3D"MsoNormal"><u=
></u>=C2=A0<u></u></p><p class=3D"MsoNormal">and yes we most likely will do=
 a micro release before February 28<u></u><u></u></p><p class=3D"MsoNormal"=
><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><di=
v style=3D"border-top:none;border-right:none;border-bottom:none;border-left=
:1.5pt solid blue;padding:0in 0in 0in 4pt"><div><div style=3D"border-right:=
none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,2=
25);padding:3pt 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size=
:11pt;font-family:Calibri,sans-serif">From:</span></b><span style=3D"font-s=
ize:11pt;font-family:Calibri,sans-serif"> Bharath Tadikonda &lt;<a href=3D"=
mailto:[email protected]" target=3D"_blank">tadikondabharath@gmail=
.com</a>&gt; <br><b>Sent:</b> Wednesday, January 21, 2026 1:36 PM<br><b>To:=
</b> <a href=3D"mailto:[email protected]" target=3D"_blank">pos=
[email protected]</a><br><b>Subject:</b> Inquiry on planned PostGI=
S releases and minor-version behavior (now=E2=80=93Feb 28)<u></u><u></u></s=
pan></p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><di=
v><p class=3D"m_2462710951653754678gmail-isselectedend">Hello PostGIS Team,=
<u></u><u></u></p><p class=3D"m_2462710951653754678gmail-isselectedend">I=
=E2=80=99m a PostgreSQL Database Engineer managing production PostgreSQL/Po=
stGIS workloads on AWS RDS/Aurora.<u></u><u></u></p><p class=3D"m_246271095=
1653754678gmail-isselectedend">We are planning a PostgreSQL <strong><span s=
tyle=3D"font-family:Aptos,sans-serif">minor upgrade</span></strong> (Postgr=
eSQL 16.6 =E2=86=92 16.11) in the near term. In our environment, past <stro=
ng><span style=3D"font-family:Aptos,sans-serif">PostGIS minor/patch release=
s</span></strong> have occasionally caused operational issues due to change=
s in function behavior, even when PostgreSQL itself was a minor upgrade. Be=
cause AWS may bundle a newer PostGIS minor version along with a PostgreSQL =
minor upgrade, we want to plan and execute testing and production rollout a=
s close together as possible.<u></u><u></u></p><p class=3D"m_24627109516537=
54678gmail-isselectedend">To help us plan safely, I wanted to ask:<u></u><u=
></u></p><ol start=3D"1" type=3D"1"><li class=3D"m_2462710951653754678gmail=
-isselectedend"><strong><span style=3D"font-family:Aptos,sans-serif">Are th=
ere any planned PostGIS releases (minor or patch) between now and February =
28?</span></strong><u></u><u></u></li></ol><ol start=3D"1" type=3D"1"><ul t=
ype=3D"circle"><li class=3D"m_2462710951653754678gmail-isselectedend">If ye=
s, which versions are anticipated?<u></u><u></u></li><li class=3D"m_2462710=
951653754678gmail-isselectedend">If not, when is the next postgis version r=
elease anticipated?<u></u><u></u></li></ul></ol><ol start=3D"2" type=3D"1">=
<li class=3D"m_2462710951653754678gmail-isselectedend"><strong><span style=
=3D"font-family:Aptos,sans-serif">For PostGIS minor/patch releases (e.g., 3=
.6.x =E2=86=92 3.6.y):</span></strong><u></u><u></u></li></ol><ol start=3D"=
2" type=3D"1"><ul type=3D"circle"><li class=3D"m_2462710951653754678gmail-i=
sselectedend">Are changes strictly bug fixes, or can they include behaviora=
l changes to existing functions?<u></u><u></u></li><li class=3D"m_246271095=
1653754678gmail-isselectedend">Are there specific classes of functions (geo=
metry processing, topology, raster, etc.) where behavior changes are more l=
ikely?<u></u><u></u></li></ul></ol><ol start=3D"3" type=3D"1"><li class=3D"=
m_2462710951653754678gmail-isselectedend"><strong><span style=3D"font-famil=
y:Aptos,sans-serif">Release notes &amp; compatibility guidance:</span></str=
ong><u></u><u></u></li></ol><ol start=3D"3" type=3D"1"><ul type=3D"circle">=
<li class=3D"m_2462710951653754678gmail-isselectedend">Is there a recommend=
ed way to identify <em><span style=3D"font-family:Aptos,sans-serif">functio=
n-level behavior changes</span></em> between minor versions (beyond high-le=
vel release notes)?<u></u><u></u></li><li class=3D"m_2462710951653754678gma=
il-isselectedend">Are there guarantees or best-practice guidance around bac=
kward compatibility expectations for PostGIS patch releases?<u></u><u></u><=
/li></ul></ol><ol start=3D"4" type=3D"1"><li class=3D"m_2462710951653754678=
gmail-isselectedend"><strong><span style=3D"font-family:Aptos,sans-serif">O=
perational best practices:</span></strong><u></u><u></u></li></ol><ol start=
=3D"4" type=3D"1"><ul type=3D"circle"><li class=3D"m_2462710951653754678gma=
il-isselectedend">Do you recommend pinning PostGIS patch versions in produc=
tion where possible, or validating only specific functions we rely on most =
during upgrades?<u></u><u></u></li></ul></ol><p class=3D"m_2462710951653754=
678gmail-isselectedend">Any guidance you can share will help us reduce risk=
 and plan upgrades more confidently.<u></u><u></u></p><p class=3D"m_2462710=
951653754678gmail-isselectedend">Thank you for your time and for all the wo=
rk you do on PostGIS.<u></u><u></u></p><p>Best regards,<br>Bharath<br>Postg=
reSQL Database Engineer<u></u><u></u></p></div></div></div></div></div></di=
v></blockquote></div>

--0000000000009e2c720648eb1104--