You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/development/releasing.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,8 +55,10 @@ Promote the container images from the staging registry to the production registr
55
55
```
56
56
57
57
58
-
## Verify and Publish the draft release
59
-
58
+
## Verifing and Publish the release
59
+
1. Now a draft release should be available on the Github Releases page for the CAPA repository: https://github.com/kubernetes-sigs/cluster-api-provider-aws/releases you should go there and verify all the relevant informations are there before undrafting the release.
60
+
1. Make sure the release notes are present in the release description.
61
+
1. Update the release description to link to the promotion image.
60
62
1. Verify that all the files below are attached to the drafted release:
61
63
1. `clusterawsadm-darwin-amd64`
62
64
1. `clusterawsadm-darwin-arm64`
@@ -82,7 +84,6 @@ Promote the container images from the staging registry to the production registr
82
84
1. `cluster-template-rosa.yaml`
83
85
1. `cluster-template-simple-clusterclass.yaml`
84
86
1. `metadata.yaml`
85
-
1. Update the release description to link to the promotion image.
86
87
1. Publish release. Use the pre-release option for release candidate versions of Cluster API Provider AWS.
87
88
1. Email `kubernetes-sig-cluster-lifecycle@googlegroups.com` to announce the release. You can use this template for the email:
0 commit comments