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: Documentation/contributor-guide/release.md
+4-7
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,8 @@ which don't need to be executed before releasing each version.
62
62
4. Authenticate the image registry, refer to [Authentication methods](https://cloud.google.com/container-registry/docs/advanced-authentication).
63
63
-`gcloud auth login`
64
64
-`gcloud auth configure-docker`
65
+
5. Install gh, refer to [GitHub's documentation](https://github.com/cli/cli#installation). Ensure that running
66
+
`gh auth login` succeeds for the GitHub account you use to contribute to etcd.
65
67
66
68
### Release steps
67
69
@@ -85,13 +87,8 @@ which don't need to be executed before releasing each version.
85
87
It generates all release binaries under the directory `/tmp/etcd-release-${VERSION}/etcd/release/` and images. Binaries are pushed to the Google Cloud bucket
86
88
under project `etcd-development`, and images are pushed to `quay.io` and `gcr.io`.
87
89
7. Publish the release page on GitHub
88
-
- Set the release title as the version name
89
-
- Choose the correct release tag (generated from step #4)
90
-
- Follow the format of previous release pages
91
-
- Attach the generated binaries and signature file
92
-
- Verify the historical binary size for each architecture. If there's a big difference, verify that it works for that architecture
93
-
- Select whether it's a pre-release
94
-
- Publish the release
90
+
- Open the **draft** release URL shown by the release script
91
+
- Review that it looks correct, then publish the release
95
92
8. Announce to the etcd-dev googlegroup
96
93
97
94
Follow the format of previous release emails sent to [email protected], see an example below. After sending out the email, ask one of the mailing list maintainers to approve the email from the pending list. Additionally, label the release email as `Release`.
Please check out [CHANGELOG](https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-${RELEASE_VERSION_MAJOR_MINOR}.md) for a full list of changes. And make sure to read [upgrade guide](https://etcd.io/docs/v${RELEASE_VERSION_MAJOR_MINOR}/upgrades/upgrade_${RELEASE_VERSION_MAJOR}_${RELEASE_VERSION_MINOR}/) before upgrading etcd (there may be breaking changes).
2
+
3
+
For installation guides, please check out [play.etcd.io](http://play.etcd.io) and [operating etcd](https://etcd.io/docs/v${RELEASE_VERSION_MAJOR_MINOR}/op-guide/). Latest support status for common architectures and operating systems can be found at [supported platforms](https://etcd.io/docs/v${RELEASE_VERSION_MAJOR_MINOR}/op-guide/supported-platform/).
etcd uses [`gcr.io/etcd-development/etcd`](https://gcr.io/etcd-development/etcd) as a primary container registry, and [`quay.io/coreos/etcd`](https://quay.io/coreos/etcd) as secondary.
0 commit comments