diff options
| author | Steve Perry <steveperry-53@users.noreply.github.com> | 2017-08-04 15:00:21 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-08-04 15:00:21 -0700 |
| commit | a17c0ecfc2ec7f02eea20e151c8b114c32965251 (patch) | |
| tree | ddad6922324e4deb9bf85e9de2940c6055587a0d | |
| parent | b56f18ef51ab102e5c8c675f55cf437fa05ccf75 (diff) | |
Change link from 1.7 to 1.8.
| -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 bb5589e6..42cd20c5 100644 --- a/contributors/devel/release/README.md +++ b/contributors/devel/release/README.md @@ -108,7 +108,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/spreadsheets/d/1IJSTd3MHorwUt8i492GQaKKuAFsZppauT4v1LJ91WHY/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/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit?usp=sharing) for 1.8). 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.8`](https://github.com/kubernetes/kubernetes.github.io/tree/release-1.8)), 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. |