diff options
| author | Ed Costello <epc@epcostello.com> | 2015-07-12 22:03:06 -0400 |
|---|---|---|
| committer | Ed Costello <epc@epcostello.com> | 2015-07-12 22:03:06 -0400 |
| commit | a284d4cf980e30a237d170cd77b8f50c8b251c3b (patch) | |
| tree | 18f1da2638aa7191644bcc9213ebf0f3d97d2edd | |
| parent | 3a38ce4217962abf1ebd37e08ea51c5c857de70e (diff) | |
Copy edits for typos
| -rw-r--r-- | releasing.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/releasing.md b/releasing.md index 6533858c..9cec89e0 100644 --- a/releasing.md +++ b/releasing.md @@ -21,7 +21,7 @@ You should progress in this strict order. #### Selecting Release Components When cutting a major/minor release, your first job is to find the branch -point. We cut `vX.Y.0` releases directly from `master`, which is also the the +point. We cut `vX.Y.0` releases directly from `master`, which is also the branch that we have most continuous validation on. Go first to [the main GCE Jenkins end-to-end job](http://go/k8s-test/job/kubernetes-e2e-gce) and next to [the Critical Builds page](http://go/k8s-test/view/Critical%20Builds) and hopefully find a @@ -42,7 +42,7 @@ Because Jenkins builds frequently, if you're looking between jobs `kubernetes-e2e-gce` build (but please check that it corresponds to a temporally similar build that's green on `kubernetes-e2e-gke-ci`). Lastly, if you're having trouble understanding why the GKE continuous integration clusters are failing -and you're trying to cut a release, don't hesistate to contact the GKE +and you're trying to cut a release, don't hesitate to contact the GKE oncall. Before proceeding to the next step: |