diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-04-11 11:00:47 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-04-11 11:00:47 -0700 |
| commit | 3fe7999cbf04864ef2b5bd49c38f190648edddab (patch) | |
| tree | 570d913bf95e9e92f88780be5f0264aa2908ede6 | |
| parent | 009eed4e90c50674186e9c92a984998068cea595 (diff) | |
| parent | 63c52e9440773827382144cb6415c6b5d30cee15 (diff) | |
Merge pull request #3422 from dims/document-code-freeze-restrictions-for-adding-conformance-tests
Document code freeze restrictions for adding conformance tests
| -rw-r--r-- | contributors/devel/sig-architecture/conformance-tests.md | 5 |
1 files changed, 5 insertions, 0 deletions
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: |