User Tools

Site Tools


wiki:development:release-howto

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
wiki:development:release-howto [2015/02/19 11:41]
ionic Typo in first dch command, should have been dch -r.
wiki:development:release-howto [2015/02/24 19:25] (current)
ionic More version updating.
Line 26: Line 26:
 |  13  | <code bash>​x2go-signtarballs</​code>​ | Automatically signs and checksums tarballs, dmg files etc. No manual work required. | |  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) | |  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. | +|  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>​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@lists.x2go.org>​. | +|  16  | <code bash>​updatebuildmain</​code>​ | Automatically update ''​build-main''​ branch. | 
-|  ​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.''​ |+|  ​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@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>git log --oneline | grep -i '​continue develop'</​code>​ | Check the last post-release commit for any other files that might include the version and need to be updated! ​|
 |  :::  | <code bash>dch -i</​code>​ |  :::  | |  :::  | <code bash>dch -i</​code>​ |  :::  |
-|  ​18   | <code bash>​debcommit -a</​code>​ | Commits the changes. ​+|  ​19   | <code bash>​debcommit -a</​code>​ | Commits the changes. |
-|  19   | FIXME JEN | FIXME KINS |+
wiki/development/release-howto.1424346119.txt.gz · Last modified: 2015/02/19 11:41 by ionic