diff options
| author | taoyu27 <yutao@chinacloud.com.cn> | 2018-02-05 11:16:56 +0800 |
|---|---|---|
| committer | taoyu27 <yutao@chinacloud.com.cn> | 2018-02-05 11:16:56 +0800 |
| commit | a6de183b6bea47bc5ee70db544d54404a1e4b24b (patch) | |
| tree | a0a7304c7d2c6b9197ebf26f2debba7ec1eb4200 | |
| parent | f367271772f6616088473a6d99a0f084266d4047 (diff) | |
fix broken link in e2e-tests.md
Signed-off-by: taoyu27 <yutao@chinacloud.com.cn>
| -rw-r--r-- | contributors/devel/e2e-tests.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index 544b546a..d37fa325 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/versioning.md#supported-releases). +as laid out in [our versioning policy](../design-proposals/release/versioning.md#supported-releases). 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: |