This is an old revision of the document!
The prerequisite for these steps is to login to japsand as x2go-admin
.
Variable | Meaning |
---|---|
<ver> | New version of the to-be-released component. |
<component> | Git name of the to-be-released component. |
No | Command | Tips / Comment |
---|---|---|
1 | cd release-manager
| |
2 | git clone ...
| Clone repository on japsand, if it doesn't already exist. |
3 | cd <component> | |
4 | git checkout master
| Only necessary, if you're not already on the master branch. Check via git status . |
5 | git pull --rebase | Always make sure the repository is up-to-date. |
6 | dch -i | Make sure to explicitly use :w in vim to save the text. Otherwise, i.e., via :x , your change will not be recorded! |
7 | git diff
| Make sure the output is exactly what you expect! |
8 | git commit -am 'release <ver>' | |
9 | git push
| |
10 | 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 gnupg system is set up correctly and you have default key set. |
11 | git push --tags | Run this on your own machine to push the new tag. |
12 | tarballrelease <ver> <ver> | Back on japsand |
13 | x2go-signtarballs | Automatically signs and checksums tarballs, dmg files etc. No manual work required. |
14 | unison X2Go-Releases.prf | Sync the current tarball directory in ~/release-manager automatically with ymir (packages.x2go.org) |
15 | updatebuildmain | Automatically update build-main branch. |
16 | x2go-release-announcements [<first> [<last>]] | Previous release announcements can be seen via setting first and last > 0 . Set first to 0 to get the current one. Copy the text into a new mail, cut and paste the first line into the mail subject. Change appropriately. Summarize the changes. Credit and thank individual people (especially translators.) GPG-Sign and send this mail to x2go-announcements@lists.x2go.org. |
17 | increment version in: .spec, VERSION | Make sure to increment the UPSTREAM version number. Revert what dhc -i did (it probably incremented the number behind x2go .) Add a descriptive message like Continue development. |
dch -i |
||
18 | debcommit -a
| Commits the changes. |
19 | ![]() | ![]() |