-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Restructure release docs stack #10354
Labels
area/release
Issues or PRs related to releasing
kind/documentation
Categorizes issue or PR as related to documentation.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
area/release
Issues or PRs related to releasing
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Apr 1, 2024
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Apr 1, 2024
/kind documentation |
k8s-ci-robot
added
the
kind/documentation
Categorizes issue or PR as related to documentation.
label
Apr 10, 2024
/priority backlog |
k8s-ci-robot
added
the
priority/backlog
Higher priority than priority/awaiting-more-evidence.
label
Apr 11, 2024
I can take this one. |
/assign |
github-project-automation
bot
moved this to Done
in CAPI v1.8 release improvement tasks
Aug 20, 2024
github-project-automation
bot
moved this from Todo
to Done
in CAPI v1.7 release improvement tasks
Aug 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/release
Issues or PRs related to releasing
kind/documentation
Categorizes issue or PR as related to documentation.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
here is the kubernetes release example: https://github.com/kubernetes/sig-release/tree/master/release-team
the idea is to split some of these lengthier docs (i.e. https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md) so they are broken up by team. this makes them easier to consume and improves the organization of the release docs
/area release
The text was updated successfully, but these errors were encountered: