From f2a13a4dcfa4f3eb948bfef1160ffb7847e988ff Mon Sep 17 00:00:00 2001 From: taoyu27 Date: Mon, 5 Feb 2018 17:25:04 +0800 Subject: [PATCH] fix broken link in e2e-tests.md Signed-off-by: taoyu27 --- contributors/devel/e2e-tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index d37fa325e..4737a4f51 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -595,7 +595,7 @@ any other labels. As each new release of Kubernetes providers new functionality, the subset of tests necessary to demonstrate conformance grows with each release. Conformance is thus considered versioned, with the same backwards compatibility guarantees -as laid out in [our versioning policy](../design-proposals/release/versioning.md#supported-releases). +as laid out in [our versioning policy](/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew). Conformance tests for a given version should be run off of the release branch that corresponds to that version. Thus `v1.2` conformance tests would be run from the head of the `release-1.2` branch. eg: