mirror of
https://git.osgeo.org/gitea/postgis/postgis
synced 2024-10-25 17:42:38 +00:00
40 lines
1.3 KiB
Plaintext
40 lines
1.3 KiB
Plaintext
How to release
|
|
~~~~~~~~~~~~~~
|
|
Date: 2006-12-15
|
|
|
|
Versioning Scheme
|
|
-----------------
|
|
|
|
Release version is composed by POSTGIS_MAJOR_VERSION, POSTGIS_MINOR_VERSION
|
|
and POSTGIS_MICRO_VERSION components.
|
|
|
|
By default only [POSTGIS_MICRO_VERSION] increments between releases.
|
|
|
|
[POSTGIS_MINOR_VERSION] is incremented (and MICRO set to 0) when minor
|
|
additions have been introduced (one or two functions can be considered
|
|
*micro* additions)
|
|
|
|
[POSTGIS_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) Add a "release mark" in ChangeLog (search for '---' at the start
|
|
of a line to see how it looks like)
|
|
3) Edit NEWS: set release date and check all notable changes are
|
|
been reported (extract from ChangeLog).
|
|
4) Edit README.postgis and set release date and version.
|
|
5) Add release notes in doc/postgis.xml
|
|
6) Commit all your changes
|
|
7) Tag the release:
|
|
$ base=http://svn.refractions.net/postgis/
|
|
$ rel=MAJ.MIN.MIC
|
|
$ svn copy -m "Tagged release $rel" $base/trunk $base/tags/$rel
|
|
8) Run: sh make_dist.sh MAJ.MIN.MIC
|
|
9) Publish
|
|
10) Announce
|
|
|