diff options
| author | Devan Carpenter <devan@ii.coop> | 2019-08-12 17:30:59 -0700 |
|---|---|---|
| committer | Devan Carpenter <devan@ii.coop> | 2019-08-12 17:30:59 -0700 |
| commit | 5663868a88e80223b09aea0394d2afe4aaccf19b (patch) | |
| tree | 5c739a57481920abd53db3c64b7087cbfc79d821 | |
| parent | 4646583182a007d444df1423316aa9426011478a (diff) | |
Conformance Tests: Reduce soak time for new tests
New tests don't need to be run for a full release-cycle before getting
promoted to Conformance. Two weeks is sufficient, and more practical.
| -rw-r--r-- | contributors/devel/sig-architecture/conformance-tests.md | 2 |
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 |