Release production

Testing or Stable release production

• Commit all changes

 dpsubcommit
 dpsubpush

• Check versions and eventually run version script
• Set geopsy pack next version

 cd admin
 dpversion A B or C
 dpversion c
 git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
 dppush

• Update configure scripts (hard coded version)

 dpsubconfig -g -f

• Commit and tag

 dpsubdo dpversion c
 dpsubdo dpversion t
 dpsubdo git tag -a geopsypack-3.1.1 -m "Release Geopsy Pack 3.1.1"
 dpsubpush -f

• Start compilation servers manually or wait for night build

Devel snapshot production

cd admin
dpversion S
dpversion c
[git tag -a geopsypack-2.1.0-snapshot-20090730 \
         -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
dppush

dpsubcommit
dpsubdo dpversion S
dpsubconfig -g -f
dpsubdo dpversion c
[dpsubdo dpversion t]
[dpsubdo git tag -a geopsypack-2.1.0-snapshot-20090730 \
                 -m "Release Geopsy Pack 2.1.0-snapshot-20090730"]
dpsubpush -f

For snapshots, tagging can be skipped (never been re-used during the past years).

Tagging

To remove a tag:

 git tag -d tag_name

Version tags

Automatic version statistics do take into account only changes of .cpp and .h files. All other modification must be checked manually.

 dpsubdo dpversion t
 dpsubpush

Geopsy Pack tags

Once all tests report success, set all version numbers as explained Version management.

Tag all sub projects

 dpsubdo git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0"
 dpsubpush -f

Tag list of projects and general options. Before tagging, check that the version of the project list has been properly changed !

 cd admin
 git tag -a geopsypack-2.1.0 -m "Release Geopsy Pack 2.1.0"
 dppush

Release Notes

Release notes are built from commit comments.

dpsubreleasenotes 2.2.1 2.3.0

Eventually edit the final file before its publication:

scp release_notes-2.3.0 geopsy.org:/var/www/geopsy/htdocs/release_notes

Publishing

Through web interface after an administrator login in "status"