diff options
| author | Andrew Chen <chenopis@users.noreply.github.com> | 2017-05-04 16:31:07 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-05-04 16:31:07 -0700 |
| commit | f0f06d2829c07986e9b4ec626a62c0df7a57fbbe (patch) | |
| tree | b3d49ae671b4e4c36965052e555ef8c4f24529c2 | |
| parent | 940fc660c18ebf6d23cb438c21d1647883bd3311 (diff) | |
fix spreadsheet link
| -rw-r--r-- | contributors/devel/release/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/release/README.md b/contributors/devel/release/README.md index 9bcd7548..0e84bd42 100644 --- a/contributors/devel/release/README.md +++ b/contributors/devel/release/README.md @@ -106,7 +106,7 @@ During the code freeze period, fix any bugs discovered with you feature, and wri ##### Writing Feature Documentation -1. Make sure your feature for the upcoming release is on the release tracking board (e.g. [link](https://docs.google.com/a/google.com/spreadsheets/d/14CuRzarSdVSU18ri7Cxyc6zZVm51vSvH_bUZNYe78tQ/edit?usp=sharing) for 1.7). +1. Make sure your feature for the upcoming release is on the release tracking board (e.g. [link](https://docs.google.com/spreadsheets/d/1IJSTd3MHorwUt8i492GQaKKuAFsZppauT4v1LJ91WHY/edit?usp=sharing) for 1.7). 2. Create a PR with documentation for your feature in the [documents repo](https://github.com/kubernetes/kubernetes.github.io). * **Your PR should target the release branch (e.g. [`release-1.7`](https://github.com/kubernetes/kubernetes.github.io/tree/release-1.6)), not the [`master`](https://github.com/kubernetes/kubernetes.github.io/tree/master) branch.** * Any changes to the master branch become live on https://kubernetes.io/docs/ as soon as they are merged, and for releases we do not want docuemntation to go live until the release is cut. |