diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-12-11 06:08:06 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-11 06:08:06 -0800 |
| commit | 9f2dce7519a9e2b56c2cf80032c2b352fa0fb926 (patch) | |
| tree | 7f7941a19ce32f52705d700276821cefc129485d | |
| parent | 1dd85f99f6a27da65d156e5d35a1125e1fa866be (diff) | |
| parent | 4b9e4b4ca4423ee2495ef351d5b374dc00796ade (diff) | |
Merge pull request #4294 from nikhita/staging-semver
sig-arch/staging: add note about semver tags
| -rw-r--r-- | contributors/devel/sig-architecture/staging.md | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/contributors/devel/sig-architecture/staging.md b/contributors/devel/sig-architecture/staging.md index b255f0fc..cbf4b5e2 100644 --- a/contributors/devel/sig-architecture/staging.md +++ b/contributors/devel/sig-architecture/staging.md @@ -14,10 +14,18 @@ At the time of this writing, the list of published branches includes: - release-1.16 / release-13.0, - and release-1.17 / release-14.0 -Kubernetes tags (e.g., v1.9.1-beta1) are also applied automatically to the published repositories, prefixed with kubernetes- (e.g., kubernetes-1.9.1-beta1). The client-go semver tags (on client-go only!) including release-notes are still done manually. +Kubernetes tags (e.g., `v1.17.0-beta.2`) are also applied automatically to the published repositories, prefixed with `kubernetes-`. +From `v1.17.0` Kubernetes release, matching semver `v0.x.y` tags are also created for each `v1.x.y` Kubernetes tag. -The semver tags are still the (well tested) official releases. The kubernetes-1.x.y tags have limited test coverage (we have some automatic tests in place in the bot), but can be used by early adopters of client-go and the other libraries. Moreover, they help to vendor the correct version of k8s.io/api and k8s.io/apimachinery. +For example, if you check out the `kubernetes-1.17.0` or the `v0.17.0` tag in +a published repo, the code you get is exactly the same as if you check out the +`v1.17.0` tag in Kubernetes, and change directory to `staging/src/k8s.io/<repo-name>`. -If further repos under staging are needed, adding them to the bot is easy. Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS). +It is recommend to use the semver `v0.x.y` tags for a seamless experience +with go modules. -Currently, the bot is hosted on a [public CNCF cluster](http://git.k8s.io/publishing-bot/k8s-publishing-bot.md). +If further repos under staging are needed, adding them to the bot is easy. +Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS). + +Currently, the bot is hosted on a +[public CNCF cluster](http://git.k8s.io/publishing-bot/k8s-publishing-bot.md). |