Release production

Testing or Stable release production

• Commit all changes

 dpsubcommit
 dpsubpush

• Check versions and eventually run version script
• Update configure scripts (hard coded version)

 dpsubconfig -g

• Commit individual versions

 dpsubdo dpversion c

If it fails, proceed to manual commit with

 dpsubcommit

The usual message for new versions is "Version X.Y.Z"

• Tag

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

• Update distribution repositories

 cd geopsypack
 dpversion A B or C
 dpgitconfigure
 git commit -a
 git push

• 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).

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

If build process successful, files are available in

 /geopsy/build/candidates

Go to

 /geopsy/build/archives

Run

 ./generate win64 testing 3.1.1 <DATE>

Follow instruction at the end to publish the files.