From 95df7dd035c936dc837ca19fa4e457dad38cf37d Mon Sep 17 00:00:00 2001 From: Christopher Angelo Phillips <32073428+spiffcs@users.noreply.github.com> Date: Tue, 14 Sep 2021 09:08:37 -0400 Subject: [PATCH] Add command examples to release documentation (#503) * update release document with commands run Signed-off-by: Christopher Angelo Phillips * small edits Signed-off-by: Christopher Angelo Phillips --- RELEASE.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 86db99f62..4d8362c26 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -87,9 +87,12 @@ This release process itself should be as automated as possible, and have only a 1. Tag the main branch with a full semantic-version, prefixed with a `v`. If there is a milestone with a partial version, the full version should be used for the git tag (e.g. - with a Milestone of `v0.1` the tag should be `v0.1.0`). + with a Milestone of `v0.1` the tag should be `v0.1.0`). You can determine the changes going + into a release by running `make changelog-unreleased`. Use this change list to determine the + release increment. After determining the release increment (major, minor, patch), create the tag. + Given the above example the command to create the tag would be `git tag v0.1.0`. -1. Push the tag. +1. Push the tag. Given the above example the command to push the tag would be `git push origin v0.1.0`. 1. A release admin must approve the release on the GitHub Actions release pipeline run page. Once approved, the release pipeline will generate all assets and draft a GitHub Release.