summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-08-06 15:18:21 -0700
committerGitHub <noreply@github.com>2018-08-06 15:18:21 -0700
commit16ae128eac411070336633add751b48bba25a890 (patch)
tree5661277086d31818caea9b64da8ce68125c9b747
parentb628b63425ffd08271e43cbc3c0a2fba8f56bacc (diff)
parent419c07d692aaf332312d6302762d3aceced93317 (diff)
Merge pull request #2460 from yujuhong/update-cri-testing
Update CRI testing policy
-rw-r--r--contributors/devel/cri-testing-policy.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/contributors/devel/cri-testing-policy.md b/contributors/devel/cri-testing-policy.md
index fb01b36e..d41de619 100644
--- a/contributors/devel/cri-testing-policy.md
+++ b/contributors/devel/cri-testing-policy.md
@@ -50,16 +50,16 @@ To publish tests results, please submit a proposal in the
briefly explaining your runtime, providing at least two maintainers, and
assigning the proposal to the leads of SIG-Node.
-These test results should be published under the `sig-node` tab, grouped by the
-runtimes, organized as follows.
+These test results should be published under the `sig-node` tab, organized
+as follows.
```
-sig-node -> sig-node-{Kubernetes-version} -> sig-node-{runtime-name} -> [page containing all test jobs]
+sig-node -> sig-node-cri-{Kubernetes-version} -> [page containing the required jobs]
```
-The `sig-node` tab only lists up to three most recent Kubernetes versions,
-including the master branch for the current release cycle, e.g.,
-`sig-node-master, sig-node-1.9, sig-node-1.8`.
+Only the last three most recent Kubernetes versions and the master branch are
+kept at any time. This is consistent with the Kubernetes release schedule and
+policy.
## Test job maintenance