[postgis-devel] postgis 1.1.0 / postgis 1.0.2

[strk at refractions.net]

Sorry, my head is flipping too fast, it must be due to 
the heat.

Releasing 1.1.0 would not take a short time, the
autoconf-based build is too young and untested.

Releasing 1.0.2 *does* make sense as it contains
bug fixes (fault tolerant btree, rtree fix, leak plugged
in pg_error, cleaner build scripts).

I've dropped buffer(0) implementation of GeomUnion in
the 1.0 branch as it would be a new feature (and we saw
it's broken already).

The only new feature left would be 8.1 support.
Leaving it in would allow more people to test new
GiST functionalities.

Again, sorry for the confusion, managing all these
branches between geos and postgis is not an easy
task in summertime ...

--strk;


On Fri, Jul 01, 2005 at 01:38:52PM +0200, Markus Schaber wrote:
> Hi, Strk,
> 
> strk at refractions.net wrote:
> > After some toughts I think there's no reason to release a
> > 1.0.2 version. Since we have the postgis_proc_upgrade.pl
> > script moving to 1.1.0 directly doesn't require a dump/reload.
> > 
> > The postgis_proc_upgrade.pl will replace all functions, it
> > is thus able to change definition of library to load (1.1 
> > instead of 1.0).
> 
> This sounds good.
> 
> > We might also release 1.0.2 from the head branch actually,
> > and rely on postgis_full_version() to report procs upgrade
> > requirement.
> 
> I would vote against releasing HEAD as 1.0.2, as I think 1.0.X should be
> reserved for bugfix-only releases, and 1.1.0 is the way for new features.
> 
> Btw, when do you plan to release 1.1.0? I've got some small work to
> finish jdbc/jts support which I'd like to finish before release :-9
> 
> Markus
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel