From 2c5f04c2c31b7499b473bee7890439ed5397e128 Mon Sep 17 00:00:00 2001 From: deeplow Date: Mon, 23 Oct 2023 08:44:09 +0100 Subject: [PATCH] Add instructions for adding release tag Instructions only stated how to verify the release tag bug not how to make it. --- RELEASE.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index db08d89..be9bd11 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -11,8 +11,14 @@ Before making a release, all of these should be complete: - [ ] Update the "Version" field in `install/linux/dangerzone.spec` - [ ] Update version and download links in `README.md`, and screenshot if necessary - [ ] CHANGELOG.md should be updated to include a list of all major changes since the last release -- [ ] There must be a PGP-signed git tag for the version, e.g. for dangerzone 0.1.0, the tag must be `v0.1.0` - [ ] Copy the entirety of these instructions onto a new issue and call it **QA and Release version \** +- [ ] Create a PGP-signed git tag for the version, e.g. for dangerzone `v0.1.0`, the is created with: + + ``` + git tag -s v0.1.0 + git push origin v0.1.0 + ``` + **Note**: release candidates are suffixed by `-rcX`. ## Large Document Testing