User Tools

Site Tools


wiki:development:release-howto-mswin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
wiki:development:release-howto-mswin [2015/02/25 13:31]
mikedep333 correct creating a branch, so that it is not based off of a nameless branch
wiki:development:release-howto-mswin [2016/09/20 22:24]
mikedep333 ver-mswin -> release/ver-mswin We've been doing this for a while.
Line 7: Line 7:
 ^ Variable ^ Meaning ^ ^ Variable ^ Meaning ^
 | ''<ver>'' | Existing released version. For example, 4.0.3.2  | | ''<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 |+| ''<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>'' | 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-YYYYMMDD-mswin>'' | Git tag for the new Windows-specific version. For example, 4.0.3.2-20150201-mswin (for February 1st, 2015) |
Line 18: Line 18:
 |  2  | <code bash>cd <component></code> | | |  2  | <code bash>cd <component></code> | |
 |  3  | <code bash>git fetch --all </code> | If the repo already exists, you will follow this step instead of step 1. | |  3  | <code bash>git fetch --all </code> | If the repo already exists, you will follow this step instead of step 1. |
-|  4  | <code bash>git checkout -b <ver-mswin> <ver> </code> | | Creates a branch off of the released tag+|  4  | <code bash>git checkout -b <release/ver-mswin> <ver> </code> | | Creates a branch off of the released tag
  
 If a branch already exists: If a branch already exists:
Line 24: Line 24:
 |  1  | <code bash>git clone ...</code> | Clone repository on on your machine (cygwin) with git, if it doesn't already exist. | |  1  | <code bash>git clone ...</code> | Clone repository on on your machine (cygwin) with git, if it doesn't already exist. |
 |  2  | <code bash>cd <component></code> | | |  2  | <code bash>cd <component></code> | |
-|  3  | <code bash>git checkout <ver-mswin></code> | Only necessary, if you're not already on the branch. Check via ''git status''. |+|  3  | <code bash>git checkout <release/ver-mswin></code> | Only necessary, if you're not already on the branch. Check via ''git status''. |
 |  4  | <code bash>git pull --rebase</code> | Always make sure the repository is up-to-date. | |  4  | <code bash>git pull --rebase</code> | Always make sure the repository is up-to-date. |
  
Line 35: Line 35:
 |  4  | <code bash>git push</code> | | |  4  | <code bash>git push</code> | |
  
-Now, perform a build with <ver-YYYYMMDD> as the version from X2Go-WinBuilder:+Now, if building X2Go Clientperform a build using Jenkins. 
 + 
 +http://jenkins.x2go.org:8080/view/All%20Releases/ 
 + 
 +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:
  
-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 http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:pyhoca-gui
  
wiki/development/release-howto-mswin.txt · Last modified: 2017/03/11 20:40 by mikedep333