Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: Update staging branch list and clarify publishing rules #8100

Merged
merged 1 commit into from
Dec 30, 2024
Merged

doc: Update staging branch list and clarify publishing rules #8100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions contributors/devel/sig-architecture/staging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,20 +6,20 @@ We publish the staging repos using the [publishing bot](https://git.k8s.io/publi

The list of staging repositories currently published is available in [staging/README.md inside of the k8s.io/kubernetes repository](https://git.k8s.io/kubernetes/staging/README.md).

At the time of this writing, the list of published branches includes:
At the time of this writing, based on [publishing rule](https://github.com/kubernetes/kubernetes/blob/9cf4f912451009296a50f267d47b484f77ce05e4/staging/publishing/rules.yaml), the list of published branches includes:

- master,
- release-1.14 / release-11.0,
- release-1.15 / release-12.0,
- release-1.16 / release-13.0,
- and release-1.17 / release-14.0
- release-1.28
- release-1.29
- release-1.30
- release-1.31

Kubernetes tags (e.g., `v1.17.0-beta.2`) are also applied automatically to the published repositories, prefixed with `kubernetes-`.
Kubernetes tags (e.g., `v1.30.0-beta.0`) 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.

For example, if you check out the `kubernetes-1.17.0` or the `v0.17.0` tag in
For example, if you check out the `kubernetes-1.30.0` or the `v0.30.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>`.
`v1.30.0` tag in Kubernetes, and change directory to `staging/src/k8s.io/<repo-name>`.

It is recommend to use the semver `v0.x.y` tags for a seamless experience
with go modules.
Expand Down