[X2Go-Commits] page changed: wiki:development:release-howto-mswin
wiki-admin at x2go.org
wiki-admin at x2go.org
Wed Sep 21 00:25:01 CEST 2016
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-YYYYMMDD -> ver-YYYY.MM.DD We've been doing this for a while now.
User : mikedep333
@@ -6,10 +6,10 @@
^ Variable ^ Meaning ^
| ''<ver>'' | Existing released version. For example, 4.0.3.2 |
| ''<release/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) |
+ | ''<ver-YYYY.MM.DD>'' | New Windows-specific version. For example, 4.0.3.2-20150201 (for February 1st, 2015) |
+ | ''<ver-YYYY.MM.DD-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.
@@ -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 <ver-YYYYMMDD> as the version from X2Go-WinBuilder:
+ If building PyHoca-GUI perform a build with <ver-YYYY.MM.DD> 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 | <code bash>git tag -s '<ver-YYYYMMDD-mswin>' -m 'Windows-Specific Release <ver-YYYYMMDD>'</code> | 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 | <code bash>git tag -s '<ver-YYYY.MM.DD-mswin>' -m 'Windows-Specific Release <ver-YYYY.MM.DD>'</code> | 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 | <code bash>git push --tags</code> | Run this **on your own machine** to push the new tag. |
| 3 | Upload the installers to code.x2go.org | FIXME: Fill in details |
| 4 | <code bash>cd <directory>> && ~/sign_packages/sighntarballs.sh</code> | 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/
More information about the x2go-commits
mailing list