[X2Go-Commits] page changed: wiki:development:release-howto

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2015/02/24 19:21
Browser     : Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:36.0) Gecko/20100101 Firefox/36.0
IP-Address  : 217.92.117.31
Hostname    : home.ionic.de
Old Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto?rev=1424346119
New Revision: http://wiki.x2go.org/doku.php/wiki:development:release-howto
Edit Summary: Add preliminary jenkins documentation.
User        : ionic

@@ -24,10 +24,10 @@
  |  11  | <code bash>git push --tags</code> | Run this **on your own machine** to push the new tag. |
  |  12  | <code bash>tarballrelease <ver> <ver></code> | Back on **japsand** |
  |  13  | <code bash>x2go-signtarballs</code> | Automatically signs and checksums tarballs, dmg files etc. No manual work required. |
  |  14  | <code bash>unison X2Go-Releases.prf</code> | Sync the current tarball directory in ''~/release-manager'' automatically with ymir (packages.x2go.org) |
- |  15
 | <code bash>updatebuildmain</code> | Automatically update ''build-main'' branch. |
- |  16  | <code bash>x2go-release-announcements [<first> [<last>]]</code> | 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 at lists.x2go.org>. |
- |  17   | <code>increment version in: .spec, VERSION</code> | 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.'' |
+ |  15  | Check Jenkins | Log in to https://jenkins.x2go.org:8443/ with your ''japsand'' username and password. Switch to the ''All Releases'' tab in the main window. Search for the component to be
released and the release branch (mostly ''main''.) Click on that build job. On the left hand side of the updated page, click on ''Configure''. Scroll down to the ''Build'' section. Check the jobs in ''Execute Shell'' statements. Make sure that all relevant distros and releases are covered, but exclude those not appropriate for the component or those known to fail. One failed subtask will ABORT all the other tasks. |
+ |  16  | <code bash>updatebuildmain</code> | Automatically update ''build-main'' branch. |
+ |  17  | <code bash>x2go-release-announcements [<first> [<last>]]</code> | 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 at lists.x2go.org>. |
+ |  18   | <code>increment
version in: .spec, VERSION</code> | 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.'' |
  |  :::  | <code bash>dch -i</code> |  :::  |
- |  18   | <code bash>debcommit -a</code> | Commits the changes. |
- |  19   | FIXME JEN | FIXME KINS |
+ |  19   | <code bash>debcommit -a</code> | Commits the changes. |



-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/