felixfoertsch/syncthing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Update release process

Browse Source
This commit is contained in:
Jakob Borg
2016-03-23 10:21:21 +01:00
parent be75b6c28a
commit 279fd90d57
1 changed files with 14 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/release-creation.rst
+14 -6
View File
@@ -30,11 +30,15 @@ push it:
$ git tag -a -s -m v0.10.15 v0.10.15 $ git tag -a -s -m v0.10.15 v0.10.15
$ git push --tags $ git push --tags
(The tag is signed with your personal key. The binary releases will be signed (The tag is signed with your personal key. The binary releases will be
by the Syncthing Release key later.) signed by the Syncthing Release key later. I use `git autotag
<https://github.com/calmh/git-autotag>`__ to do this correcly with minimal
pain.)
Trigger the ``syncthing-release`` job for the newly created Trigger the ``syncthing-release`` job for the newly created tag and wait for
tag and wait for it to complete successfully before moving on. it to complete successfully before moving on. This builds the
``syncthing-release-windows``, ``syncthing-release-mac`` and
``syncthing-release-debian`` jobs as well, and these must succeed.
Run ``go run script/changelog.go`` (in the repo) to create the changelog Run ``go run script/changelog.go`` (in the repo) to create the changelog
comparison from the previous release. Copy to clipboard. comparison from the previous release. Copy to clipboard.
@@ -45,7 +49,11 @@ the changelog from above, and publish the release.
On the signing server, logged in via ssh, run ``sign-upload-release``. This On the signing server, logged in via ssh, run ``sign-upload-release``. This
will download the build artefacts from Jenkins, sign all the binaries, will download the build artefacts from Jenkins, sign all the binaries,
create the sha1sum and sha256sum files, sign them with the release GPG key and create the sha1sum and sha256sum files, sign them with the release GPG key
upload the whole shebang to Github. and upload the whole shebang to Github.
Verify it looks sane on the releases page. Verify it looks sane on the releases page.
Then run ``sign-upload-debian`` which does the same for the Debian packages
-- downloads them, signs the package archive, and pushes the new archive to
the web server.