Update documents for release process
This commit is contained in:
@@ -134,7 +134,7 @@ git clone git@github.com:kubernetes/kubernetes.git
|
||||
cd kubernetes
|
||||
```
|
||||
|
||||
or `git checkout upstream/master` from an existing repo.
|
||||
or `git fetch upstream && git checkout upstream/master` from an existing repo.
|
||||
|
||||
Decide what version you're cutting and export it:
|
||||
|
||||
@@ -210,9 +210,10 @@ release](https://github.com/kubernetes/kubernetes/releases/new):
|
||||
1. fill in the release title from the draft;
|
||||
1. re-run the appropriate release notes tool(s) to pick up any changes people
|
||||
have made;
|
||||
1. find the appropriate `kubernetes.tar.gz` in GCS, download it, double check
|
||||
the hash (compare to what you had in the release notes draft), and attach it
|
||||
to the release; and
|
||||
1. find the appropriate `kubernetes.tar.gz` in [GCS bucket](https://
|
||||
console.developers.google.com/storage/browser/kubernetes-release/release/),
|
||||
download it, double check the hash (compare to what you had in the release
|
||||
notes draft), and attach it to the release; and
|
||||
1. publish!
|
||||
|
||||
## Injecting Version into Binaries
|
||||
|
Reference in New Issue
Block a user