Browse Source

Add PR step to release instructions

Michael Bridgen 1 year ago
parent
commit
43a0fa6a8f
1 changed files with 7 additions and 5 deletions
  1. 7
    5
      internal_docs/releasing.md

+ 7
- 5
internal_docs/releasing.md View File

@@ -9,11 +9,13 @@ This process will create a new tagged release of flux, push dockerfiles and uplo
9 9
 
10 10
 1. Alter and commit the /CHANGELOG.md file to signify what has changed in this version.
11 11
 2. Ensure example deployment is up-to-date. (Check image tags)
12
-3. Create a new release: https://github.com/weaveworks/flux/releases/new
13
-4. Fill in the version number for the name and tag. The version number should conform to [semver](semver.org); i.e., look like `1.2.3` (NB: no leading 'v'); optionally with a pre-release suffix, e.g., `1.0.0-beta`
14
-5. Fill in the Description field (possibly a copy paste from the CHANGELOG.md)
15
-6. Click "Publish release"
16
-7. Add a new release to https://checkpoint-api.weave.works/admin
12
+3 Push that to a PR and have it reviewed.
13
+  3.1 Merge!
14
+4. Create a new release: https://github.com/weaveworks/flux/releases/new
15
+5. Fill in the version number for the name and tag. The version number should conform to [semver](semver.org); i.e., look like `1.2.3` (NB: no leading 'v'); optionally with a pre-release suffix, e.g., `1.0.0-beta`
16
+6. Fill in the Description field (possibly a copy paste from the CHANGELOG.md)
17
+7. Click "Publish release"
18
+8. Add a new release to https://checkpoint-api.weave.works/admin
17 19
 
18 20
 Circle will then run the build and upload the built binaries to the "Downloads" section of the release.
19 21
 

Loading…
Cancel
Save