summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2019-08-20 14:55:15 -0700
committerGitHub <noreply@github.com>2019-08-20 14:55:15 -0700
commitc36741e8cfce972021ee3d5938e324ac66298863 (patch)
tree4bf0f375072071f7e54414aff24d953532c060c4
parent14cc2532b534deca50f078d1867bfac6a52bae2f (diff)
parent5663868a88e80223b09aea0394d2afe4aaccf19b (diff)
Merge pull request #3996 from devaips/new-test-soak-period
Conformance Tests: Reduce soak time for new tests
-rw-r--r--contributors/devel/sig-architecture/conformance-tests.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/sig-architecture/conformance-tests.md b/contributors/devel/sig-architecture/conformance-tests.md
index 7c2aae22..6db41d10 100644
--- a/contributors/devel/sig-architecture/conformance-tests.md
+++ b/contributors/devel/sig-architecture/conformance-tests.md
@@ -51,7 +51,7 @@ specifically, a test is eligible for promotion to conformance if:
- it passes against the appropriate versions of kubernetes as spelled out in
the [conformance test version skew policy]
- it is stable and runs consistently (e.g., no flakes), and has been running
- for at least one release cycle
+ for at least two weeks
- new conformance tests or updates to conformance tests for additional scenarios
are only allowed before code freeze dates set by the release team to allow
enough soak time of the changes and gives folks a chance to kick the tires