<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
p.gmail-isselectedend, li.gmail-isselectedend, div.gmail-isselectedend
{mso-style-name:gmail-isselectedend;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1754818607;
mso-list-template-ids:1733829672;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link="#467886" vlink="#96607D" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Bharath,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The best advice I can give is to look at the upcoming NEWS items<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEWS">https://gitea.osgeo.org/postgis/postgis/src/branch/stable-3.6/NEWS</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>and yes we most likely will do a micro release before February 28<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Bharath Tadikonda <tadikondabharath@gmail.com> <br><b>Sent:</b> Wednesday, January 21, 2026 1:36 PM<br><b>To:</b> postgis-users@lists.osgeo.org<br><b>Subject:</b> Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=gmail-isselectedend>Hello PostGIS Team,<o:p></o:p></p><p class=gmail-isselectedend>I’m a PostgreSQL Database Engineer managing production PostgreSQL/PostGIS workloads on AWS RDS/Aurora.<o:p></o:p></p><p class=gmail-isselectedend>We are planning a PostgreSQL <strong><span style='font-family:"Aptos",sans-serif'>minor upgrade</span></strong> (PostgreSQL 16.6 → 16.11) in the near term. In our environment, past <strong><span style='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. Because AWS may bundle a newer PostGIS minor version along with a PostgreSQL minor upgrade, we want to plan and execute testing and production rollout as close together as possible.<o:p></o:p></p><p class=gmail-isselectedend>To help us plan safely, I wanted to ask:<o:p></o:p></p><ol start=1 type=1><li class=gmail-isselectedend style='mso-list:l0 level1 lfo1'><strong><span style='font-family:"Aptos",sans-serif'>Are there any planned PostGIS releases (minor or patch) between now and February 28?</span></strong><o:p></o:p></li></ol><ol start=1 type=1><ul type=circle><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>If yes, which versions are anticipated?<o:p></o:p></li><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>If not, when is the next postgis version release anticipated?<o:p></o:p></li></ul></ol><ol start=2 type=1><li class=gmail-isselectedend style='mso-list:l0 level1 lfo1'><strong><span style='font-family:"Aptos",sans-serif'>For PostGIS minor/patch releases (e.g., 3.6.x → 3.6.y):</span></strong><o:p></o:p></li></ol><ol start=2 type=1><ul type=circle><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>Are changes strictly bug fixes, or can they include behavioral changes to existing functions?<o:p></o:p></li><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>Are there specific classes of functions (geometry processing, topology, raster, etc.) where behavior changes are more likely?<o:p></o:p></li></ul></ol><ol start=3 type=1><li class=gmail-isselectedend style='mso-list:l0 level1 lfo1'><strong><span style='font-family:"Aptos",sans-serif'>Release notes & compatibility guidance:</span></strong><o:p></o:p></li></ol><ol start=3 type=1><ul type=circle><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>Is there a recommended way to identify <em><span style='font-family:"Aptos",sans-serif'>function-level behavior changes</span></em> between minor versions (beyond high-level release notes)?<o:p></o:p></li><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>Are there guarantees or best-practice guidance around backward compatibility expectations for PostGIS patch releases?<o:p></o:p></li></ul></ol><ol start=4 type=1><li class=gmail-isselectedend style='mso-list:l0 level1 lfo1'><strong><span style='font-family:"Aptos",sans-serif'>Operational best practices:</span></strong><o:p></o:p></li></ol><ol start=4 type=1><ul type=circle><li class=gmail-isselectedend style='mso-list:l0 level2 lfo1'>Do you recommend pinning PostGIS patch versions in production where possible, or validating only specific functions we rely on most during upgrades?<o:p></o:p></li></ul></ol><p class=gmail-isselectedend>Any guidance you can share will help us reduce risk and plan upgrades more confidently.<o:p></o:p></p><p class=gmail-isselectedend>Thank you for your time and for all the work you do on PostGIS.<o:p></o:p></p><p>Best regards,<br>Bharath<br>PostgreSQL Database Engineer<o:p></o:p></p></div></div></div></div></body></html>