[X2Go-Commits] page changed: wiki:development:release-howto-mswin
A page in your DokuWiki was added or changed. Here are the details: Date: 2016/09/20 22:36 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 IP-Address : 96.248.86.25 Hostname: pool-96-248-86-25.cmdnnj.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin?rev=1474410301 New Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin Edit Summary: Steps for build-main-mswin branch User: mikedep333 @@ -32,8 +32,19 @@ | 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 ' | | | 4 | git push | | + + Update the build-main-mswin branch. If you created a branch earlier: + ^ No ^ Command ^ Tips / Comment ^ + | 1 | git branch -f build-main-mswin | + | 2 | Ask the X2Go git admin to run the same command on the server | Currently, Ionic is the admin | + + If you did not create a branch earlier: + ^ No ^ Command ^ Tips / Comment ^ + | 1 | git checkout build-main-mswin | | + | 2 | git merge --ff-only | | + | 3 | git push | | Now, if building X2Go Client, perform a build using Jenkins. http://jenkins.x2go.org:8080/view/All%20Releases/ -- This mail was generated by DokuWiki at http://wiki.x2go.org/ ___ x2go-commits mailing list x2go-commits@lists.x2go.org http://lists.x2go.org/listinfo/x2go-commits
[X2Go-Commits] page changed: wiki:development:release-howto-mswin
A page in your DokuWiki was added or changed. Here are the details: Date: 2016/09/20 22:25 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 IP-Address : 96.248.86.25 Hostname: pool-96-248-86-25.cmdnnj.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin?rev=1474410244 New Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin Edit Summary: ver-MMDD -> ver-.MM.DD We've been doing this for a while now. User: mikedep333 @@ -6,10 +6,10 @@ ^ Variable ^ Meaning ^ | | Existing released version. For example, 4.0.3.2 | | | Branch off of a released version. For example, 4.0.3.2-mswin | - | | New Windows-specific version. For example, 4.0.3.2-20150201 (for February 1st, 2015) | - | | Git tag for the new Windows-specific version. For example, 4.0.3.2-20150201-mswin (for February 1st, 2015) | + | | New Windows-specific version. For example, 4.0.3.2-20150201 (for February 1st, 2015) | + | | Git tag for the new Windows-specific version. For example, 4.0.3.2-20150201-mswin (for February 1st, 2015) | | | Git name of the to-be-released component. | Create a branch if it DNE. @@ -40,17 +40,17 @@ After completed, the build will be uploaded under [[http://code.x2go.org/releases/binary-win32/x2goclient/heuler/|the heuler folder]] (and will not have the git commit hash in its filename, which sets it apart from the nightly builds.) - If building PyHoca-GUI perform a build with as the version from X2Go-WinBuilder: + If building PyHoca-GUI perform a build with as the version from X2Go-WinBuilder: 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 '' -m 'Windows-Specific Release ' | 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. | + | 1 | git tag -s '' -m 'Windows-Specific Release ' | 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 | FIXME: Fill in details | | 4 | cd > && ~/sign_packages/sighntarballs.sh | On code.x2go.org via SSH. Automatically signs and checksums tarballs, dmg files etc. No manual work required. | -- This mail was generated by DokuWiki at http://wiki.x2go.org/ ___ x2go-commits mailing list x2go-commits@lists.x2go.org http://lists.x2go.org/listinfo/x2go-commits
[X2Go-Commits] page changed: wiki:development:release-howto-mswin
A page in your DokuWiki was added or changed. Here are the details: Date: 2016/09/20 22:24 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36 IP-Address : 96.248.86.25 Hostname: pool-96-248-86-25.cmdnnj.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin?rev=1438317116 New Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto-mswin Edit Summary: ver-mswin -> release/ver-mswin We've been doing this for a while. User: mikedep333 @@ -5,9 +5,9 @@ Also to code.x2go.org via SSH. ^ Variable ^ Meaning ^ | | Existing released version. For example, 4.0.3.2 | - | | Branch off of a released version. For example, 4.0.3.2-mswin | + | | Branch off of a released version. For example, 4.0.3.2-mswin | | | New Windows-specific version. For example, 4.0.3.2-20150201 (for February 1st, 2015) | | | Git tag for the new Windows-specific version. For example, 4.0.3.2-20150201-mswin (for February 1st, 2015) | | | Git name of the to-be-released component. | @@ -16,15 +16,15 @@ ^ No ^ Command ^ Tips / Comment ^ | 1 | git clone ... | Clone repository on on your machine (cygwin) with git, if it doesn't already exist. | | 2 | cd | | | 3 | git fetch --all | If the repo already exists, you will follow this step instead of step 1. | - | 4 | git checkout -b| | Creates a branch off of the released tag + | 4 | git checkout -b| | Creates a branch off of the released tag 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 | | - | 3 | git checkout | Only necessary, if you're not already on the branch. Check via ''git status''. | + | 3 | git checkout | 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: -- This mail was generated by DokuWiki at http://wiki.x2go.org/ ___ x2go-commits mailing list x2go-commits@lists.x2go.org http://lists.x2go.org/listinfo/x2go-commits
