diff options
| author | Filip Grzadkowski <filipg@google.com> | 2015-11-25 14:50:46 +0100 |
|---|---|---|
| committer | Filip Grzadkowski <filipg@google.com> | 2015-12-10 19:28:40 +0100 |
| commit | 7da888eee00d0ca825059b7ceaf05dbdecceaf38 (patch) | |
| tree | 2259af18e2ecb57ba694b0f125d8a0bf24849fb7 | |
| parent | 9b60d8c88083958918bb92b6104b1fe8d4e9b9ec (diff) | |
Update documents for release process
| -rw-r--r-- | releasing.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/releasing.md b/releasing.md index 757048ad..3cefb725 100644 --- a/releasing.md +++ b/releasing.md @@ -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 |