Difference between revisions of "Release production"
Line 22: | Line 22: | ||
== Testing == | == Testing == | ||
− | + | The build process is tested automatically every day for Linux, Windows and Mac OS distributions. [http://www.geopsy.org/download/nextrelease.php Daily reports] | |
− | + | An automatic testbench would be helpful. | |
− | |||
− | |||
== Versions == | == Versions == |
Revision as of 19:17, 19 September 2019
Contents
Summary
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
For snapshots, tagging can be skipped (never been re-used during the past years).
Testing
The build process is tested automatically every day for Linux, Windows and Mac OS distributions. Daily reports
An automatic testbench would be helpful.
Versions
Make sure that versions of individual packages are properly set. See Version management for details.
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"