Skip to content

Update ci-signal handbook to reflect updated process for dropping unsupported versions #12025

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

Jump to bottom
Open
shecodesmagic opened this issue Mar 24, 2025 · 1 comment · May be fixed by #12057
Open

Update ci-signal handbook to reflect updated process for dropping unsupported versions #12025

shecodesmagic opened this issue Mar 24, 2025 · 1 comment · May be fixed by #12057
Labels
area/release Issues or PRs related to releasing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@shecodesmagic
Copy link

Currently, the ci-signal handbook instructs the ci-signal team to drop outdated test-infra logic and unsupported versions during Step 3 and 4 of "Setup jobs and dashboards for a new release branch."

However, during the v1.10 release cycle, it was decided to retain support for v1.7 even after creating jobs and dashboards for v1.10. The plan is to drop support for v1.7 after the end of the release cycle, not during the setup phase.

I'm opening this issue to get consensus on where in the process this step should happen and ensure we capture the correct task and timing in the handbook. Once we align, we can update the handbook accordingly.

/area release
/kind cleanup
@k8s-ci-robot k8s-ci-robot added area/release Issues or PRs related to releasing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 24, 2025
@chrischdi
Copy link
Member

/triage accepted
/priority important-longterm
/kind documentation

After the minor release (e.g. in this cycle after the v1.10.0 release), we should drop the jobs for the n-3 release (in this cycle the v1.7 release branch).

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/documentation Categorizes issue or PR as related to documentation. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. labels Mar 25, 2025
@shecodesmagic shecodesmagic linked a pull request Apr 6, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release Issues or PRs related to releasing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
3 participants
@chrischdi @k8s-ci-robot @shecodesmagic