From 2534d0390a0ec17c2a95c4fda237b7918bd38bc1 Mon Sep 17 00:00:00 2001 From: redshiftzero Date: Mon, 17 Jun 2019 14:57:13 -0700 Subject: [PATCH] README: release management guide for alpha releases --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 2845db47c..1c927842d 100644 --- a/README.md +++ b/README.md @@ -123,6 +123,16 @@ but developers should merge their migration into the latest migration that has b release. The above mentioned autogenerate command will not do this for you. +## Making a Release + +**Note:** These are the release guidelines for pre-production alpha releases. Production release tags must +be signed with the SecureDrop release key. + +1. Update versions: `./update_version.sh $new_version_number`. +2. Commit the changes with commit message `securedrop-client $new_version_number` and make a PR. +3. You should confirm via a manual debian package build and manual testing in Qubes that there are no regressions (this is limited pre-release QA). +4. Once your PR is approved, you can add a tag and push: `git tag $new_version_number`. + ## Qubes Debugging Using a version of this application installed from a deb package in Qubes,