github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Copy edits for typos

Browse Source
This commit is contained in:
Ed Costello
2015-07-12 22:03:06 -04:00
parent a1efb50a29
commit 98e9f1eeae
20 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/devel/releasing.md
View File

@@ -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: