mirror of
https://github.com/syncthing/syncthing.git
synced 2026-04-08 16:38:03 -04:00
52 lines
1.5 KiB
ReStructuredText
52 lines
1.5 KiB
ReStructuredText
Creating a Release
|
|
==================
|
|
|
|
Prerequisites
|
|
-------------
|
|
|
|
- Push access to the ``syncthing`` repo, for pushing a new tag.
|
|
|
|
- SSH account on the signing server.
|
|
|
|
Process
|
|
-------
|
|
|
|
Make sure the build seems sane. I.e. the build is clean on the build
|
|
server, the integration tests pass without complaints.
|
|
|
|
Update the documentation and translations, and commit the result.
|
|
|
|
.. code-block:: bash
|
|
|
|
$ ./build.sh prerelease
|
|
$ git commit -m "Translation and docs update"
|
|
$ git push
|
|
|
|
Create a new, signed tag on master, with the version as comment, and
|
|
push it:
|
|
|
|
.. code-block:: bash
|
|
|
|
$ git tag -a -s -m v0.10.15 v0.10.15
|
|
$ git push --tags
|
|
|
|
(The tag is signed with your personal key. The binary releases will be signed
|
|
by the Syncthing Release key later.)
|
|
|
|
Trigger the ``syncthing-release`` job for the newly created
|
|
tag and wait for it to complete successfully before moving on.
|
|
|
|
Run ``go run script/changelog.go`` (in the repo) to create the changelog
|
|
comparison from the previous release. Copy to clipboard.
|
|
|
|
On the Github releases page, select the newly pushed tag and hit "Edit
|
|
Tag". Set the "Release title" to the same version as the tag, paste in
|
|
the changelog from above, and publish the release.
|
|
|
|
On the signing server, logged in via ssh, run ``sign-upload-release``. This
|
|
will create download the build artefacts from Jenkins, sign all the binaries,
|
|
create the sha1sum and sha256sum files, sign them with the release GPG key and
|
|
upload the whole shebang to Github.
|
|
|
|
Verify it looks sane on the releases page.
|