[postgis-devel] [geos-devel] Toward 3.5.0 release

Sandro Santilli strk at keybit.net
Tue Aug 4 06:27:17 PDT 2015


On Tue, Aug 04, 2015 at 08:59:31AM -0400, Greg Troxel wrote:
> 
> Sandro Santilli <strk at keybit.net> writes:
> 
> > On Tue, Aug 04, 2015 at 08:15:02AM -0400, Paragon Corporation wrote:
> >> > Did anyone respond to the call-for-testing on geos lists ?
> >> What call?  People, especially package maintainers don't like testing stuff
> >> unless it's in an unchanging tar ball.
> >
> > Uhm, I though you sent a call for testing, evidently you didn't.
> > Would tagging an RC1 give packagers an unchanging tarball ?
> 
> I actually did run tests, but I made my own tarball.  I think I posted a
> note about it, but it seemed to build/run/check ok on NetBSD 6 i386.
> 
> As a package maintainer, what I'd like for testing is a distfile that's
> just like what would be released, except with a different version.  And
> of course it should unpack to a name consistent with the tarball and
> version.  Basically the output of "make dist", and in cases where that
> really is how releases are generated, it's easy enough to do myself.

That's how releases are made, indeed.
The version/directory name is 3.5.0dev during development, not
changing at every commit.

> The other big thing for packaging is that once a file is published with
> a version number, it can be withdrawn, but no file with the same name
> and different contents should be published.

If it helps, we could tag a 3.5.0-rc1 for testing purposes.
But we're still talking about tests from packagers and developers,
more than tests from users. Package users would only handle to test
the official 3.5.0, and we'll still support the 3.5 branch with
bugfixes as we are currently doing for 3.3 and 3.4 branches.

--strk;



More information about the postgis-devel mailing list