Difference between revisions of "Release production"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | == | + | == Version setup == |
* Commit all changes | * Commit all changes | ||
Line 36: | Line 36: | ||
* Start compilation servers manually or wait for night build | * Start compilation servers manually or wait for night build | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Release Notes == | == Release Notes == |
Revision as of 13:10, 28 July 2020
Version setup
- 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
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
- Copy files to download/archives
- Run on all platforms and follow instructions at the end
dpgitcontents dpgitversions