[postgis-devel] 2.2.2 Release (?)

[Greg Troxel]

Paul Ramsey <pramsey at cleverelephant.ca> writes:

> In light of the upgrade blocker that is now gone, I'd like to propose
> a 2.2.2 in short order. Does anyone have a list of other open tickets
> that are critical to address prior to a 2.2.2?

I know of nothing that's necessary, but I'm sort of paged out these few
weeks.

Partly on general principles and partly because there were bugs in one
of the recent releases only caught at packaging time (unintended file
moving), I will make my usual suggestion of creating/publishing an RC,
having a freeze except for documentation fixes, and waiting 7 days
between RC publication and release, to give users and packagers a chance
to pre-stage an update and validate it.


(My impression is that there isn't a script to run to generate a release
From svn, because the script that is used has to make tags and actually
do svn ops.  So a random user can't make an tarball for testing.  It
would be nice to have this be more like automake's "make dist", which
just needs a source tree and doesn't write to the VCS.  But until then,
I think RCs are in order.)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20160228/2700324b/attachment.sig>