From pramsey at cleverelephant.ca  Mon Dec 15 13:26:54 2025
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Mon, 15 Dec 2025 13:26:54 -0800
Subject: CI on master
Message-ID: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com>

Master has been red on github since this commit to topology

https://github.com/postgis/postgis/commit/b0dcc8510fd7930752db4e65a9e7f368b63a139c

Komzpa this is yours, can you sort it?

P
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251215/c81618f4/attachment.htm>

From lr at pcorp.us  Mon Dec 15 14:57:37 2025
From: lr at pcorp.us (Regina Obe)
Date: Mon, 15 Dec 2025 17:57:37 -0500
Subject: CI on master
In-Reply-To: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com>
References: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com>
Message-ID: <000001dc6e16$356d8ca0$a048a5e0$@pcorp.us>

Looks like it?s failing on GEOS 3.9.  Since we?ve already EOL?d GEOS 3.9  https://libgeos.org/usage/download/ , 

 

should we just up our base GEOS for 3.7 to 3.10? 

 

I can swap out that pg14- geos39  for a pg14-geos310 and see if it passes.

 

 

 

From: Paul Ramsey <pramsey at cleverelephant.ca> 
Sent: Monday, December 15, 2025 4:27 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: CI on master

 

Master has been red on github since this commit to topology

 

https://github.com/postgis/postgis/commit/b0dcc8510fd7930752db4e65a9e7f368b63a139c

 

Komzpa this is yours, can you sort it?

 

P

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251215/b82e737a/attachment-0001.htm>

From lr at pcorp.us  Mon Dec 15 15:00:06 2025
From: lr at pcorp.us (Regina Obe)
Date: Mon, 15 Dec 2025 18:00:06 -0500
Subject: CI on master
References: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com> 
Message-ID: <000501dc6e16$8f0fb760$ad2f2620$@pcorp.us>

FWIW woodie is running 3.10 and it passes

 

https://woodie.osgeo.org/repos/30/pipeline/3889/18#L313

 

So I?m assuming 3.10 will pass even though we don?t have any GHA geos 3.10 ci.

 

From: Regina Obe <lr at pcorp.us> 
Sent: Monday, December 15, 2025 5:58 PM
To: 'Paul Ramsey' <pramsey at cleverelephant.ca>; 'PostGIS Development Discussion' <postgis-devel at lists.osgeo.org>
Subject: RE: CI on master

 

Looks like it?s failing on GEOS 3.9.  Since we?ve already EOL?d GEOS 3.9  https://libgeos.org/usage/download/ , 

 

should we just up our base GEOS for 3.7 to 3.10? 

 

I can swap out that pg14- geos39  for a pg14-geos310 and see if it passes.

 

 

 

From: Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca> > 
Sent: Monday, December 15, 2025 4:27 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> >
Subject: CI on master

 

Master has been red on github since this commit to topology

 

https://github.com/postgis/postgis/commit/b0dcc8510fd7930752db4e65a9e7f368b63a139c

 

Komzpa this is yours, can you sort it?

 

P

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251215/a8bddd3b/attachment.htm>

From pramsey at cleverelephant.ca  Mon Dec 15 15:05:14 2025
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Mon, 15 Dec 2025 15:05:14 -0800
Subject: CI on master
In-Reply-To: <000001dc6e16$356d8ca0$a048a5e0$@pcorp.us>
References: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com>
 <000001dc6e16$356d8ca0$a048a5e0$@pcorp.us>
Message-ID: <893431AA-9051-4F33-8849-EC3ACB400144@cleverelephant.ca>



> On Dec 15, 2025, at 2:57?PM, Regina Obe <lr at pcorp.us> wrote:
> 
> Looks like it?s failing on GEOS 3.9.  Since we?ve already EOL?d GEOS 3.9  https://libgeos.org/usage/download/ ,  

> should we just up our base GEOS for 3.7 to 3.10? 


Yes, I think that makes sense.

P


>  I can swap out that pg14- geos39  for a pg14-geos310 and see if it passes.
>    From: Paul Ramsey <pramsey at cleverelephant.ca> 
> Sent: Monday, December 15, 2025 4:27 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: CI on master
>  Master has been red on github since this commit to topology
>  https://github.com/postgis/postgis/commit/b0dcc8510fd7930752db4e65a9e7f368b63a139c
>  Komzpa this is yours, can you sort it?
>  P



From lr at pcorp.us  Mon Dec 15 21:17:27 2025
From: lr at pcorp.us (Regina Obe)
Date: Tue, 16 Dec 2025 00:17:27 -0500
Subject: CI on master
In-Reply-To: <893431AA-9051-4F33-8849-EC3ACB400144@cleverelephant.ca>
References: <CACowWR2G2ae97cG7exngVu1Rvc2yukbVpTJba6ddsFSn2shQ_w@mail.gmail.com>
 <000001dc6e16$356d8ca0$a048a5e0$@pcorp.us>
 <893431AA-9051-4F33-8849-EC3ACB400144@cleverelephant.ca>
Message-ID: <002501dc6e4b$4575c1a0$d06144e0$@pcorp.us>

> > On Dec 15, 2025, at 2:57?PM, Regina Obe <lr at pcorp.us> wrote:
> >
> > Looks like it?s failing on GEOS 3.9.  Since we?ve already EOL?d GEOS
> > 3.9  https://libgeos.org/usage/download/ ,
> 
> > should we just up our base GEOS for 3.7 to 3.10?
> 
> 
> Yes, I think that makes sense.
> 
> P
> 
> 
> >  I can swap out that pg14- geos39  for a pg14-geos310 and see if it passes.
> >    From: Paul Ramsey <pramsey at cleverelephant.ca>
> > Sent: Monday, December 15, 2025 4:27 PM
> > To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> > Subject: CI on master
> >  Master has been red on github since this commit to topology
> >
> https://github.com/postgis/postgis/commit/b0dcc8510fd7930752db4e65a9e7
> > f368b63a139c  Komzpa this is yours, can you sort it?
> >  P


Okay I've swapped out pg14/geos3.9 testing with 

Pg14/geos 3.10 and it's passing:

https://github.com/postgis/postgis/actions/runs/20257107239/job/58161404254






From strk at kbt.io  Tue Dec 16 05:05:15 2025
From: strk at kbt.io (Sandro Santilli)
Date: Tue, 16 Dec 2025 14:05:15 +0100
Subject: Collaboration Interest: AI Guidance for PostGIS in pg-aiguide
In-Reply-To: <CAJnEWwk79veuOY-nhYcMfP_6w=hTFZ_9PnaCbboCd+2ysy+4oA@mail.gmail.com>
References: <CADsUR0C0mcOBrQVu979qMEQzO2usOqHXoe2MK43BbM145i1apg@mail.gmail.com>
 <CAC8Q8tKGqXFSdKx=0XkKWhdsoX40a=nybVFUBDa7zLGMYk7bXg@mail.gmail.com>
 <CADsUR0C2jz-WRKkPTFQLAZOtBC5penX_pk28RdixTz9=CbSjvQ@mail.gmail.com>
 <CAC8Q8tK55udAmRNZ3V8Hr_zF_R0xYGg9-cOiPo9yPVSgPJxr1g@mail.gmail.com>
 <CAJnEWwk79veuOY-nhYcMfP_6w=hTFZ_9PnaCbboCd+2ysy+4oA@mail.gmail.com>
Message-ID: <aUFZC0ilnNk0sl3m@oli>

On Sun, Nov 30, 2025 at 10:12:40PM +0100, Imre Samu wrote:

> If it proves useful, this could also be the seed of an osgeo-focused skills repo,

Could you please share a link to this osgeo-focused skills repo ?

--strk; 

  Libre GIS consultant/developer ?
  https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251216/c8deba2f/attachment.sig>

From strk at kbt.io  Tue Dec 16 05:08:12 2025
From: strk at kbt.io (Sandro Santilli)
Date: Tue, 16 Dec 2025 14:08:12 +0100
Subject: PSC Vote: EOL PostGIS 3.0 and 3.1
In-Reply-To: <000e01dc5ff6$94bc6380$be352a80$@pcorp.us>
References: <000e01dc5ff6$94bc6380$be352a80$@pcorp.us>
Message-ID: <aUFZvLGbObnI512G@oli>

+1 for shipping final 3.0 and 3.1 releases and mark the branches EOL

--strk;

On Thu, Nov 27, 2025 at 06:35:56PM -0500, Regina Obe wrote:
> In my last request for vote, it seemed people didn't feel I went far enough.
> Some wanted 3.1 - 3.4 EOL'd as well.
> 
> I feel that is a bit too drastic, but I'm willing to go for 3.1 as well.
> 
> +1
> 
> Darafei already expressed a +1
> 
> I presume Paul is a +1 too ?
> https://lists.osgeo.org/pipermail/postgis-devel/2025-November/030668.html
> though a bit ambiguous
> 
> Anyone else have an opinion to the contrary, before I mark these 2 EOL.
> 
> Note I'll do a final release of these before I mark them EOL as there are
> quite a few bug tickets in there for these.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251216/83eed1bf/attachment.sig>

From strk at kbt.io  Tue Dec 16 05:08:54 2025
From: strk at kbt.io (Sandro Santilli)
Date: Tue, 16 Dec 2025 14:08:54 +0100
Subject: PSC Vote: Remove support for PostgreSQL 12 and PostgreSQL 13 in
 PostGIS 3.7
In-Reply-To: <000f01dc5ff7$64d73ae0$2e85b0a0$@pcorp.us>
References: <000f01dc5ff7$64d73ae0$2e85b0a0$@pcorp.us>
Message-ID: <aUFZ5uuVf_KUBHW-@oli>

On Thu, Nov 27, 2025 at 06:41:46PM -0500, Regina Obe wrote:
> I think it's time to say bye to support for PostgreSQL 12 and PostgreSQL 13
> for master branch.

+1 --strk;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251216/6511f219/attachment-0001.sig>

From me at komzpa.net  Mon Dec 22 17:07:16 2025
From: me at komzpa.net (=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?=)
Date: Tue, 23 Dec 2025 05:07:16 +0400
Subject: PSC Vote: accept h3_pg under PostGIS umbrella
Message-ID: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>

Hi,

Recently Zacharias Knudsen, maintainer of h3_pg, reached out to me asking
about helping maintain the project. The library itself is hosted on github,
https://github.com/zachasme/h3-pg, acts as extension to postgres and
postgis and is already shipped by all the major Postgres vendors (including
AWS and PGDG). The license of code is Apache 2.0 matching the license of h3
library itself. I am already pushing the library forward by making sure
there are some pull requests for features we needed when using the
extension.

Proposal: following example of postgis-docker, move the project
under PostGIS umbrella. That will include:
 - move the repository from Zach's personal github under postgis/h3-pg and
bless the new location as upstream.
 - make sure PostGIS PSC has enough rights to publish new versions on PGXN.
 - make sure Zach can still participate as maintainer of the library (has
write access / publishing rights).

Starting with:
+1 Darafei

We had preliminary discussions with Zach and PSC about it and it seems like
a way to go.

Thanks,
Darafei.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251223/3fe25b2d/attachment.htm>

From pramsey at cleverelephant.ca  Mon Dec 22 19:22:03 2025
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Mon, 22 Dec 2025 19:22:03 -0800
Subject: PSC Vote: accept h3_pg under PostGIS umbrella
In-Reply-To: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
References: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
Message-ID: <CACowWR1A2Odsg0_uiRx+v6kpnHJfpwxE4YYQK5ohm8qnunCKOg@mail.gmail.com>

+1 sounds like a solid plan

On Mon, Dec 22, 2025 at 5:07?PM Darafei "Kom?pa" Praliaskouski <
me at komzpa.net> wrote:

> Hi,
>
> Recently Zacharias Knudsen, maintainer of h3_pg, reached out to me asking
> about helping maintain the project. The library itself is hosted on github,
> https://github.com/zachasme/h3-pg, acts as extension to postgres and
> postgis and is already shipped by all the major Postgres vendors (including
> AWS and PGDG). The license of code is Apache 2.0 matching the license of h3
> library itself. I am already pushing the library forward by making sure
> there are some pull requests for features we needed when using the
> extension.
>
> Proposal: following example of postgis-docker, move the project
> under PostGIS umbrella. That will include:
>  - move the repository from Zach's personal github under postgis/h3-pg and
> bless the new location as upstream.
>  - make sure PostGIS PSC has enough rights to publish new versions on PGXN.
>  - make sure Zach can still participate as maintainer of the library (has
> write access / publishing rights).
>
> Starting with:
> +1 Darafei
>
> We had preliminary discussions with Zach and PSC about it and it seems
> like a way to go.
>
> Thanks,
> Darafei.
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251222/332420fa/attachment.htm>

From lr at pcorp.us  Tue Dec 23 06:57:02 2025
From: lr at pcorp.us (Regina Obe)
Date: Tue, 23 Dec 2025 09:57:02 -0500
Subject: PSC Vote: accept h3_pg under PostGIS umbrella
In-Reply-To: <CACowWR1A2Odsg0_uiRx+v6kpnHJfpwxE4YYQK5ohm8qnunCKOg@mail.gmail.com>
References: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
 <CACowWR1A2Odsg0_uiRx+v6kpnHJfpwxE4YYQK5ohm8qnunCKOg@mail.gmail.com>
Message-ID: <000001dc741c$66154ad0$323fe070$@pcorp.us>

+1

 

From: Paul Ramsey <pramsey at cleverelephant.ca> 
Sent: Monday, December 22, 2025 10:22 PM
To: Darafei Kom?pa Praliaskouski <me at komzpa.net>
Cc: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>; Zacharias Knudsen <z at chari.as>
Subject: Re: PSC Vote: accept h3_pg under PostGIS umbrella

 

+1 sounds like a solid plan

 

On Mon, Dec 22, 2025 at 5:07?PM Darafei "Kom?pa" Praliaskouski <me at komzpa.net <mailto:me at komzpa.net> > wrote:

Hi,

Recently Zacharias Knudsen, maintainer of h3_pg, reached out to me asking about helping maintain the project. The library itself is hosted on github, https://github.com/zachasme/h3-pg, acts as extension to postgres and postgis and is already shipped by all the major Postgres vendors (including AWS and PGDG). The license of code is Apache 2.0 matching the license of h3 library itself. I am already pushing the library forward by making sure there are some pull requests for features we needed when using the extension.

 

Proposal: following example of postgis-docker, move the project under PostGIS umbrella. That will include:
 - move the repository from Zach's personal github under postgis/h3-pg and bless the new location as upstream.
 - make sure PostGIS PSC has enough rights to publish new versions on PGXN.
 - make sure Zach can still participate as maintainer of the library (has write access / publishing rights).

Starting with:
+1 Darafei

We had preliminary discussions with Zach and PSC about it and it seems like a way to go.

Thanks,
Darafei.




 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251223/2940b36e/attachment.htm>

From strk at kbt.io  Sun Dec 28 04:50:17 2025
From: strk at kbt.io (Sandro Santilli)
Date: Sun, 28 Dec 2025 13:50:17 +0100
Subject: PSC Vote: accept h3_pg under PostGIS umbrella
In-Reply-To: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
References: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
Message-ID: <A37CFE22-0748-4060-AAE8-2AB959FFFA6E@kbt.io>

+1

thanks 

On December 23, 2025 2:07:16 AM GMT+01:00, "Darafei "Kom?pa" Praliaskouski" <me at komzpa.net> wrote:
>Hi,
>
>Recently Zacharias Knudsen, maintainer of h3_pg, reached out to me asking
>about helping maintain the project. The library itself is hosted on github,
>https://github.com/zachasme/h3-pg, acts as extension to postgres and
>postgis and is already shipped by all the major Postgres vendors (including
>AWS and PGDG). The license of code is Apache 2.0 matching the license of h3
>library itself. I am already pushing the library forward by making sure
>there are some pull requests for features we needed when using the
>extension.
>
>Proposal: following example of postgis-docker, move the project
>under PostGIS umbrella. That will include:
> - move the repository from Zach's personal github under postgis/h3-pg and
>bless the new location as upstream.
> - make sure PostGIS PSC has enough rights to publish new versions on PGXN.
> - make sure Zach can still participate as maintainer of the library (has
>write access / publishing rights).
>
>Starting with:
>+1 Darafei
>
>We had preliminary discussions with Zach and PSC about it and it seems like
>a way to go.
>
>Thanks,
>Darafei.

-- 
Sent from hand-held device with K-9 Mail. Please excuse my brevity.

From me at komzpa.net  Tue Dec 30 00:55:25 2025
From: me at komzpa.net (=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?=)
Date: Tue, 30 Dec 2025 12:55:25 +0400
Subject: PSC Vote: accept h3_pg under PostGIS umbrella
In-Reply-To: <A37CFE22-0748-4060-AAE8-2AB959FFFA6E@kbt.io>
References: <CAC8Q8t+oSq-ShEPpzujGWo7J9kFmbkYX9ytV5tVuRcb0Dyte_A@mail.gmail.com>
 <A37CFE22-0748-4060-AAE8-2AB959FFFA6E@kbt.io>
Message-ID: <CAC8Q8t+NH8nooYtkKfTGHcuwrog1kRoBzaioOJwdQDep_w6OdQ@mail.gmail.com>

With a total +4 I call the vote passed and welcome h3_pg under postgis
umbrella.

Created new team, added myself and Zach:
https://github.com/orgs/postgis/teams/h3
Repository is transferred: https://github.com/postgis/h3-pg

Pull requests are welcome :)

Thanks,
Darafei

On Sun, Dec 28, 2025 at 4:50?PM Sandro Santilli <strk at kbt.io> wrote:

> +1
>
> thanks
>
> On December 23, 2025 2:07:16 AM GMT+01:00, "Darafei "Kom?pa"
> Praliaskouski" <me at komzpa.net> wrote:
> >Hi,
> >
> >Recently Zacharias Knudsen, maintainer of h3_pg, reached out to me asking
> >about helping maintain the project. The library itself is hosted on
> github,
> >https://github.com/zachasme/h3-pg, acts as extension to postgres and
> >postgis and is already shipped by all the major Postgres vendors
> (including
> >AWS and PGDG). The license of code is Apache 2.0 matching the license of
> h3
> >library itself. I am already pushing the library forward by making sure
> >there are some pull requests for features we needed when using the
> >extension.
> >
> >Proposal: following example of postgis-docker, move the project
> >under PostGIS umbrella. That will include:
> > - move the repository from Zach's personal github under postgis/h3-pg and
> >bless the new location as upstream.
> > - make sure PostGIS PSC has enough rights to publish new versions on
> PGXN.
> > - make sure Zach can still participate as maintainer of the library (has
> >write access / publishing rights).
> >
> >Starting with:
> >+1 Darafei
> >
> >We had preliminary discussions with Zach and PSC about it and it seems
> like
> >a way to go.
> >
> >Thanks,
> >Darafei.
>
> --
> Sent from hand-held device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20251230/ee192a38/attachment.htm>