Release production

From GeopsyWiki
Jump to navigation Jump to search

Summary

Snapshot production

dpsubcommit -gui
dpsubdo dpversion S
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
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

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

Testing

For Windows and Source distributions, the build process is tested automatically every night. Daily reports

For Mac OS X, the process is also automatic but it does not run independently on a dedicated server. Instead, it is run manually (buying and installing a dedicated server, e.g. a Mac Mini would be enough, would rather help).

Versions

Make sure that versions of individual packages are properly set. See Version management for details.

Tagging

Version tags

 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.

dpsubdo git log --format="%s%n%b" geopsypack-2.2.1..geopsypack-2.3.0 \
>> ~/devel/Geopsy.org/testing/notes
cat notes | grep -v "#######" > release_notes-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"

Updating Qt Libraries

(To edit once switching to Qt 4.7)