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

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

Ok, thanks for the clarification.

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

> As Paul mentioned, we don=E2=80=99t have tentative date plans.   We relea=
se when
> we feel there are enough bug fixes in the list to make it worthwhile or i=
f
> enough time has passed.
>
> At the moment we generally don=E2=80=99t make a decision to release until=
 about a
> week before we release.
>
>
>
> Not sure what you mean by GEOS/PROJ changes.  Those are separate projects
> from PostGIS.  PostGIS just relies on them.
>
>
>
>
>
>
>
> *From:* Bharath Tadikonda <[email protected]>
> *Sent:* Wednesday, January 21, 2026 2:38 PM
> *To:* Regina Obe <[email protected]>
> *Cc:* [email protected]
> *Subject:* Re: Inquiry on planned PostGIS releases and minor-version
> behavior (now=E2=80=93Feb 28)
>
>
>
> 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 thi=
s
> 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
>
>

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

<div dir=3D"ltr">Ok, thanks for the clarification.=C2=A0</div><br><div clas=
s=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_att=
r">On Wed, Jan 21, 2026 at 2:56=E2=80=AFPM Regina Obe &lt;<a href=3D"mailto=
:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div class=3D"msg1949245497673475638"><div lang=3D=
"EN-US" style=3D"overflow-wrap: break-word;"><div class=3D"m_19492454976734=
75638WordSection1"><p class=3D"MsoNormal">As Paul mentioned, we don=E2=80=
=99t have tentative date plans.=C2=A0 =C2=A0We release when we feel there a=
re enough bug fixes in the list to make it worthwhile or if enough time has=
 passed.<u></u><u></u></p><p class=3D"MsoNormal">At the moment we generally=
 don=E2=80=99t make a decision to release until about a week before we rele=
ase.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p cla=
ss=3D"MsoNormal">Not sure what you mean by GEOS/PROJ changes.=C2=A0 Those a=
re separate projects from PostGIS.=C2=A0 PostGIS just relies on them.<u></u=
><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoN=
ormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u><=
/p><div style=3D"border-top:none;border-right:none;border-bottom:none;borde=
r-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,225);padding:3pt 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"fon=
t-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style=3D"=
font-size:11pt;font-family:Calibri,sans-serif"> Bharath Tadikonda &lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">tadikondabharath=
@gmail.com</a>&gt; <br><b>Sent:</b> Wednesday, January 21, 2026 2:38 PM<br>=
<b>To:</b> Regina Obe &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">=
[email protected]</a>&gt;<br><b>Cc:</b> <a href=3D"mailto:[email protected]=
eo.org" target=3D"_blank">[email protected]</a><br><b>Subject:<=
/b> Re: Inquiry on planned PostGIS releases and minor-version behavior (now=
=E2=80=93Feb 28)<u></u><u></u></span></p></div></div><p class=3D"MsoNormal"=
><u></u>=C2=A0<u></u></p><div><div><p class=3D"MsoNormal">Hi Regina,<u></u>=
<u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div>=
<p class=3D"MsoNormal"><i><span style=3D"color:black">&quot;and yes we most=
 likely will do a micro release before February 28&quot;=C2=A0</span></i><u=
></u><u></u></p><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><=
div><p>Could you please let us know if there is a tentative date planned fo=
r this micro release? Additionally, will this release include any changes t=
o <strong><span style=3D"font-family:Aptos,sans-serif">GEOS</span></strong>=
 or <strong><span style=3D"font-family:Aptos,sans-serif">PROJ</span></stron=
g>?<u></u><u></u></p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u=
></p><div><div><p class=3D"MsoNormal">On Wed, Jan 21, 2026 at 2:09<span sty=
le=3D"font-family:Arial,sans-serif">=E2=80=AF</span>PM Regina Obe &lt;<a hr=
ef=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt; wrote:<u></=
u><u></u></p></div><blockquote style=3D"border-top:none;border-right:none;b=
order-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0i=
n 6pt;margin-left:4.8pt;margin-right:0in"><div><div><div><p class=3D"MsoNor=
mal">Bharath,<u></u><u></u></p><p class=3D"MsoNormal">=C2=A0<u></u><u></u><=
/p><p class=3D"MsoNormal">The best advice I can give is to look at the upco=
ming NEWS items<u></u><u></u></p><p class=3D"MsoNormal">=C2=A0<u></u><u></u=
></p><p class=3D"MsoNormal"><a href=3D"https://gitea.osgeo.org/postgis/post=
gis/src/branch/stable-3.6/NEWS" target=3D"_blank">https://gitea.osgeo.org/p=
ostgis/postgis/src/branch/stable-3.6/NEWS</a><u></u><u></u></p><p class=3D"=
MsoNormal">=C2=A0<u></u><u></u></p><p class=3D"MsoNormal">and yes we most l=
ikely will do a micro release before February 28<u></u><u></u></p><p class=
=3D"MsoNormal">=C2=A0<u></u><u></u></p><p class=3D"MsoNormal">=C2=A0<u></u>=
<u></u></p><div style=3D"border-top:none;border-right:none;border-bottom:no=
ne;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,225);padding:3pt 0in 0in"><p class=3D"MsoNormal"><b><span styl=
e=3D"font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span s=
tyle=3D"font-size:11pt;font-family:Calibri,sans-serif"> Bharath Tadikonda &=
lt;<a href=3D"mailto:[email protected]" target=3D"_blank">tadikond=
[email protected]</a>&gt; <br><b>Sent:</b> Wednesday, January 21, 2026 1:3=
6 PM<br><b>To:</b> <a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a><br><b>Subject:</b> Inquiry on=
 planned PostGIS releases and minor-version behavior (now=E2=80=93Feb 28)</=
span><u></u><u></u></p></div></div><p class=3D"MsoNormal">=C2=A0<u></u><u><=
/u></p><div><div><p class=3D"m_1949245497673475638m2462710951653754678gmail=
-isselectedend">Hello PostGIS Team,<u></u><u></u></p><p class=3D"m_19492454=
97673475638m2462710951653754678gmail-isselectedend">I=E2=80=99m a PostgreSQ=
L Database Engineer managing production PostgreSQL/PostGIS workloads on AWS=
 RDS/Aurora.<u></u><u></u></p><p class=3D"m_1949245497673475638m24627109516=
53754678gmail-isselectedend">We are planning a PostgreSQL <strong><span sty=
le=3D"font-family:Aptos,sans-serif">minor upgrade</span></strong> (PostgreS=
QL 16.6 =E2=86=92 16.11) in the near term. In our environment, past <strong=
><span style=3D"font-family:Aptos,sans-serif">PostGIS minor/patch releases<=
/span></strong> have occasionally caused operational issues due to changes =
in function behavior, even when PostgreSQL itself was a minor upgrade. Beca=
use AWS may bundle a newer PostGIS minor version along with a PostgreSQL mi=
nor upgrade, we want to plan and execute testing and production rollout as =
close together as possible.<u></u><u></u></p><p class=3D"m_1949245497673475=
638m2462710951653754678gmail-isselectedend">To help us plan safely, I wante=
d to ask:<u></u><u></u></p><ol start=3D"1" type=3D"1"><li class=3D"m_194924=
5497673475638m2462710951653754678gmail-isselectedend"><strong><span style=
=3D"font-family:Aptos,sans-serif">Are there any planned PostGIS releases (m=
inor or patch) between now and February 28?</span></strong><u></u><u></u></=
li></ol><ol start=3D"1" type=3D"1"><ul type=3D"circle"><li class=3D"m_19492=
45497673475638m2462710951653754678gmail-isselectedend">If yes, which versio=
ns are anticipated?<u></u><u></u></li><li class=3D"m_1949245497673475638m24=
62710951653754678gmail-isselectedend">If not, when is the next postgis vers=
ion release anticipated?<u></u><u></u></li></ul></ol><ol start=3D"2" type=
=3D"1"><li class=3D"m_1949245497673475638m2462710951653754678gmail-isselect=
edend"><strong><span style=3D"font-family:Aptos,sans-serif">For PostGIS min=
or/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_=
1949245497673475638m2462710951653754678gmail-isselectedend">Are changes str=
ictly bug fixes, or can they include behavioral changes to existing functio=
ns?<u></u><u></u></li><li class=3D"m_1949245497673475638m246271095165375467=
8gmail-isselectedend">Are there specific classes of functions (geometry pro=
cessing, topology, raster, etc.) where behavior changes are more likely?<u>=
</u><u></u></li></ul></ol><ol start=3D"3" type=3D"1"><li class=3D"m_1949245=
497673475638m2462710951653754678gmail-isselectedend"><strong><span style=3D=
"font-family:Aptos,sans-serif">Release notes &amp; compatibility guidance:<=
/span></strong><u></u><u></u></li></ol><ol start=3D"3" type=3D"1"><ul type=
=3D"circle"><li class=3D"m_1949245497673475638m2462710951653754678gmail-iss=
electedend">Is there a recommended way to identify <em><span style=3D"font-=
family:Aptos,sans-serif">function-level behavior changes</span></em> betwee=
n minor versions (beyond high-level release notes)?<u></u><u></u></li><li c=
lass=3D"m_1949245497673475638m2462710951653754678gmail-isselectedend">Are t=
here guarantees or best-practice guidance around backward compatibility exp=
ectations for PostGIS patch releases?<u></u><u></u></li></ul></ol><ol start=
=3D"4" type=3D"1"><li class=3D"m_1949245497673475638m2462710951653754678gma=
il-isselectedend"><strong><span style=3D"font-family:Aptos,sans-serif">Oper=
ational 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_1949245497673475638m24627=
10951653754678gmail-isselectedend">Do you recommend pinning PostGIS patch v=
ersions in production where possible, or validating only specific functions=
 we rely on most during upgrades?<u></u><u></u></li></ul></ol><p class=3D"m=
_1949245497673475638m2462710951653754678gmail-isselectedend">Any guidance y=
ou can share will help us reduce risk and plan upgrades more confidently.<u=
></u><u></u></p><p class=3D"m_1949245497673475638m2462710951653754678gmail-=
isselectedend">Thank you for your time and for all the work you do on PostG=
IS.<u></u><u></u></p><p>Best regards,<br>Bharath<br>PostgreSQL Database Eng=
ineer<u></u><u></u></p></div></div></div></div></div></div></blockquote></d=
iv></div></div></div></div></blockquote></div>

--00000000000023dd7b0648eb5710--