From 63c52e9440773827382144cb6415c6b5d30cee15 Mon Sep 17 00:00:00 2001 From: Davanum Srinivas Date: Wed, 13 Mar 2019 17:15:26 -0400 Subject: Document code freeze restrictions for adding conformance tests Bugs are ok, but features are not ok during code freeze. Change-Id: I5d9e6602396735ee5798792527a0a7110ce02275 --- contributors/devel/sig-architecture/conformance-tests.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/contributors/devel/sig-architecture/conformance-tests.md b/contributors/devel/sig-architecture/conformance-tests.md index d726094e..c016b25e 100644 --- a/contributors/devel/sig-architecture/conformance-tests.md +++ b/contributors/devel/sig-architecture/conformance-tests.md @@ -47,6 +47,11 @@ 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) +- 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 + either in the community CI or their own infrastructure to make sure the tests + are robust Examples of features which are not currently eligible for conformance tests: -- cgit v1.2.3