[postgis-devel] Win32 crashes with PostGIS 1.1.4 / PostgreSQL
8.2 -- solved
Markus Schaber
schabi at logix-tt.com
Fri Oct 13 05:28:42 PDT 2006
Hi, Strk,
strk at refractions.net wrote:
>> What do you think about the attached formulation for HOWTO_RELEASE?
>
> No attachment... ?
Oh, sorry, I forgot it. :-(
It's attached now. (I hope. :-)
>> Btw, AFAICS the loader/dumper currently don't include that version info
>> altogether, they only contain the SVN version. Should we add a UTIL_* here?
>
> loader/dumper show RCSId when called w/out args, that'd help.
Yes, that's what I meant with "contain the SVN version".
But it won't change the uers confusion between PostGIS release numbers,
and SVN versions I mentioned below.
>> It might make sense to change Version.config to contain only the
>> REL_*_VERSION variables, and use them everywhere. There's a low risk
>> that we'll have users upgrade more parts then necessary, e. G. if the
>> loader and the jdbc don't change in a minor release. But as we won't
>> have independent releases of those subprojects, we confuse users even
>> more when we release a PostGIS 1.1.9 that contains a jdbc_1.1.8.jar and
>> a shp2gpsql version 4711.
>
> Yes, I've been thinknig about this too. Sounds much easier :)
So I'll create those changes soon after the next minor release.
> BTW, I see no critical fixes advertised in the CHANGES file, what did I miss ?
So, I'm afraid that Mark either forgot to mention the fixes in the
CHANGES file, or forgot to commit altogether. He announces the Win32
fixes in
http://postgis.refractions.net/pipermail/postgis-devel/2006-October/002284.html
which you kinda acknowledged in
http://postgis.refractions.net/pipermail/postgis-devel/2006-October/002285.html
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
-------------- next part --------------
How to release
~~~~~~~~~~~~~~
Date: 2006-09-27
Versioning Scheme
-----------------
Release version is composed by REL_MAJOR_VERSION, REL_MINOR_VERSION
and REL_MICRO_VERSION components. "REL" here matches SO for the server
side of PostGIS, and JDBC for the java side.
By default only [REL_MICRO_VERSION] increments between releases.
[REL_MINOR_VERSION] is incremented (and MICRO set to 0) when minor
additions have been introduced (one or two functions can be considered
*micro* additions)
[REL_MAJOR_VERSION] is incremented (and MICRO and MINOR set to 0) when
a dump/reload of existing spatial databases is *REQUIRED* for things
to work or rather *HIGHLY RECOMMENDED* to get new functionalities.
Release procedure
-----------------
1) Update Version.config as specified in Versioning Scheme above.
2) Edit CHANGES: set release date and check all notable changes are
been reported.
3) Add release notes in doc/postgis.xml
4) Tag the release:
$ base=http://svn.refractions.net/postgis/
$ rel=MAJ.MIN.MIC
$ svn copy -m "Tagged release $rel" $base/trunk $base/tags/$rel
5) Run: sh make_dist.sh MAJ.MIN.MIC
6) Publish
7) Announce