The prerequisite for these steps is to login to japsand as
| ||New version of the to-be-released component.|
| ||Git name of the to-be-released component.|
|No||Command||Tips / Comment|
git clone ...
|Clone repository on japsand, if it doesn't already exist.|
git checkout master
| Only necessary, if you're not already on the
git pull --rebase
|Always make sure the repository is up-to-date.|
| Make sure to explicitly use
|Make sure the output is exactly what you expect!|
git commit -am 'release <ver>'
git tag -s '<ver>' -m 'Upstream version <ver>'
| Run this on your own machine in your checked-out, updated copy (see steps 2 to 5.) Make sure your
git push --tags
|Run this on your own machine to push the new tag.|
tarballrelease <ver> <ver>
|Back on japsand|
|Automatically signs and checksums tarballs, dmg files etc. No manual work required.|
| Sync the current tarball directory in
|15||Check Jenkins|| Log in to https://jenkins.x2go.org:8443/ with your
| Automatically update
x2go-release-announcements [<first> [<last>]]
| Previous release announcements can be seen via setting first and last
increment version in: .spec, VERSION
| Make sure to increment the UPSTREAM version number. Revert what
git log --oneline | grep -i 'continue develop'
|Check the last post-release commit for any other files that might include the version and need to be updated!|
|Commits the changes.|