Skip to content

Commit 9f2dce7

Browse files
authored
Merge pull request #4294 from nikhita/staging-semver
sig-arch/staging: add note about semver tags
2 parents 1dd85f9 + 4b9e4b4 commit 9f2dce7

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

contributors/devel/sig-architecture/staging.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,18 @@ At the time of this writing, the list of published branches includes:
1414
- release-1.16 / release-13.0,
1515
- and release-1.17 / release-14.0
1616

17-
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.
17+
Kubernetes tags (e.g., `v1.17.0-beta.2`) are also applied automatically to the published repositories, prefixed with `kubernetes-`.
18+
From `v1.17.0` Kubernetes release, matching semver `v0.x.y` tags are also created for each `v1.x.y` Kubernetes tag.
1819

19-
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.
20+
For example, if you check out the `kubernetes-1.17.0` or the `v0.17.0` tag in
21+
a published repo, the code you get is exactly the same as if you check out the
22+
`v1.17.0` tag in Kubernetes, and change directory to `staging/src/k8s.io/<repo-name>`.
2023

21-
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).
24+
It is recommend to use the semver `v0.x.y` tags for a seamless experience
25+
with go modules.
2226

23-
Currently, the bot is hosted on a [public CNCF cluster](http://git.k8s.io/publishing-bot/k8s-publishing-bot.md).
27+
If further repos under staging are needed, adding them to the bot is easy.
28+
Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS).
29+
30+
Currently, the bot is hosted on a
31+
[public CNCF cluster](http://git.k8s.io/publishing-bot/k8s-publishing-bot.md).

0 commit comments

Comments
 (0)