Sidebar
wiki:development:release-howto-mswin
This is an old revision of the document!
General Steps
These steps assume you have access to the X2Go WinBuilder VM, which runs on top of Japsand.
Also to code.x2go.org via SSH.
| Variable | Meaning |
|---|---|
<ver> | Existing released version. For example, 4.0.3.2 |
<ver-mswin> | Branch off of a released version. For example, 4.0.3.2-mswin |
<ver-YYYYMMDD> | New Windows-specific version. For example, 4.0.3.2-20150201 (for February 1st, 2015) |
<ver-YYYYMMDD-mswin> | Git tag for the new Windows-specific version. For example, 4.0.3.2-20150201-mswin (for February 1st, 2015) |
<component> | Git name of the to-be-released component. |
Create a branch if it DNE.
| No | Command | Tips / Comment |
|---|---|---|
| 1 | git clone ...
| Clone repository on on your machine (cygwin) with git, if it doesn't already exist. |
| 2 | cd <component> | |
| 3 | git checkout master
| Only necessary, if you're not already on the master branch. Check via git status. |
| 4 | git pull --rebase | Always make sure the repository is up-to-date. |
| 5 | git checkout <ver> | |
| 6 | git checkout -b <ver-mswin> |
If a branch already exists:
| No | Command | Tips / Comment |
|---|---|---|
| 1 | git clone ...
| Clone repository on on your machine (cygwin) with git, if it doesn't already exist. |
| 2 | cd <component> | |
| 3 | git checkout <ver-mswin> | Only necessary, if you're not already on the branch. Check via git status. |
| 4 | git pull --rebase | Always make sure the repository is up-to-date. |
Continue with the release process:
| No | Command | Tips / Comment |
|---|---|---|
| 1 | dch -r | Make sure to explicitly use :w in vim to save the text. Otherwise, i.e., via :x, your change will not be recorded! Also, this needs to be updated for cygwin. |
| 2 | git diff
| Make sure the output is exactly what you expect! |
| 3 | git commit -am 'release <ver>' | |
| 4 | git push
|
Now, perform a build with <ver-YYYYMMDD> as the version from X2Go-WinBuilder:
http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:pyhoca-gui
And do some testing. Your friendly neighborhood Windows maintainer (mike#2) always SFTPs the NSIS installers to his personal Windows desktop, and then tests them there.
Once tested:
| 1 | git tag -s '<ver-YYYYMMDD-mswin>' -m 'Windows-Specific Release <ver-YYYYMMDD>' | 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. |
| 2 | git push --tags | Run this on your own machine to push the new tag. |
| 3 | Upload the installers to code.x2go.org |  : Fill in details |
| 4 | x2go-signtarballs | On code.x2go.org via SSH. Automatically signs and checksums tarballs, dmg files etc. No manual work required. |
Follow-Up:
- Update symlink via SSH or SFTP: http://code.x2go.org/releases/PyHoca-GUI_latest_mswin32-setup.exe or http://code.x2go.org/releases/PyHoca-GUI_latest_mswin32-setup.exe
- Update link on home page http://wiki.x2go.org/doku.php
- Update BOTH links here http://wiki.x2go.org/doku.php/doc:installation:x2goclient or here http://wiki.x2go.org/doku.php/doc:installation:pyhoca-gui?&#ms_windows
- Windows-Specific release notes http://wiki.x2go.org/doku.php/doc:release-notes-mswin
- Release email
wiki/development/release-howto-mswin.1424739189.txt.gz · Last modified: 2015/02/24 00:53 by mikedep333
Imprint & Legal Disclaimer -
Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3