public inbox for [email protected]
help / color / mirror / Atom feedFrom: Justin Pryzby <[email protected]>
To: Devrim Gündüz <[email protected]>
Cc: [email protected]
Subject: Re: postgis for beta releases
Date: Sat, 11 Jul 2020 11:46:20 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote:
> On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote:
> > Would you consider building packages during beta ?
>
> You mean PostGIS 3.1? I thought I pushed it already :(
I think the postgis that exists for the stable release(12) should also be built
for the beta release(13). That allows test upgrades by 1) installing same
postgis for new postgres; and 2) pg_upgrade.
Whether to build a new version of postgis is a separate question, but if you
do, I'd suggest to build for both versions of postgres when possible. That
allows choice of which to upgrade first.
During beta period in previous years, postgis has been the one important thing
missing. That requires us to drop our postgis columns for beta testing. Last
year for the first time, I instead built postgis locally on a couple servers.
I think most packages aren't built for beta, which is no problem (although I
think they sometimes needed to be added after the fact). These are on our
list: pg_repack, fincore, libpqxx-devel.
--
Justin
view thread (52+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: postgis for beta releases
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox