3rd-party/catch2
1
0
Fork 0
mirror of https://github.com/catchorg/Catch2.git synced 2024-11-22 05:16:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update release-process.md for v3

Browse Source
This commit is contained in:
Martin Hořeňovský 2022-01-03 23:30:39 +01:00
parent f4af9f6926
commit 244680d512
No known key found for this signature in database
GPG Key ID: DE48307B8B0D381A
1 changed files with 8 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/release-process.md
View File

@ -40,14 +40,10 @@ After version number is incremented, single-include header is regenerated and re
After pushing changes to GitHub, GitHub release *needs* to be created. After pushing changes to GitHub, GitHub release *needs* to be created.
Tag version and release title should be same as the new version, Tag version and release title should be same as the new version,
description should contain the release notes for the current release. description should contain the release notes for the current release.
Single header version of `catch.hpp` *needs* to be attached as a binary, We also attach the two amalgamated files as "binaries".
as that is where the official download link links to. Preferably
it should use linux line endings. All non-bundled reporters (Automake, TAP,
TeamCity, SonarQube) should also be attached as binaries, as they might be
dependent on a specific version of the single-include header.
Since 2.5.0, the release tag and the "binaries" (headers) should be PGP Since 2.5.0, the release tag and the "binaries" (amalgamated files) should
signed. be PGP signed.
#### Signing a tag #### Signing a tag
@ -57,16 +53,14 @@ is the version being released, e.g. `git tag -s v2.6.0`.
Use the version name as the short message and the release notes as Use the version name as the short message and the release notes as
the body (long) message. the body (long) message.
#### Signing the headers #### Signing the amalgamated files
This will create ASCII-armored signatures for the headers that are This will create ASCII-armored signatures for the two amalgamated files
uploaded to the GitHub release: that are uploaded to the GitHub release:
``` ```
$ gpg2 --armor --output catch.hpp.asc --detach-sig catch.hpp gpg --armor --output extras/catch_amalgamated.hpp.asc --detach-sig extras/catch_amalgamated.hpp
$ gpg2 --armor --output catch_reporter_automake.hpp.asc --detach-sig catch_reporter_automake.hpp gpg --armor --output extras/catch_amalgamated.cpp.asc --detach-sig extras/catch_amalgamated.cpp
$ gpg2 --armor --output catch_reporter_teamcity.hpp.asc --detach-sig catch_reporter_teamcity.hpp
$ gpg2 --armor --output catch_reporter_tap.hpp.asc --detach-sig catch_reporter_tap.hpp
``` ```
_GPG does not support signing multiple files in single invocation._ _GPG does not support signing multiple files in single invocation._