Revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations

[xmudrii]

What should be cleaned up or changed:

We should revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations to make sure values are still valid. This is especially important because we added stable4 version marker not so long ago. While I went through annotations when adding stable4, I think I might missed some of them, so double checking values to be sure would be nice.

For example, this annotation might be missing one periodic interval:

test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml

Line 134 in 2d42d0d

fork-per-release-periodic-interval: 6h 24h

Provide any links for context:

See #29387 for more details

This should be done before removing jobs for 1.24

/priority important-soon
/milestone v1.28
cc @kubernetes/release-engineering

[k8s-ci-robot]

@xmudrii: The provided milestone is not valid for this repository. Milestones in this repository: [someday, v1.24, v1.25]

Use /milestone clear to clear the milestone.

In response to this:

What should be cleaned up or changed:

We should revisit values for fork-per-release-periodic-interval and fork-per-release-cron annotations to make sure values are still valid. This is especially important because we added stable4 version marker not so long ago. While I went through annotations when adding stable4, I think I might missed some of them, so double checking values to be sure would be nice.

For example, this annotation might be missing one periodic interval:

test-infra/config/jobs/kubernetes/sig-release/release-branch-jobs/1.27.yaml

Line 134 in 2d42d0d

fork-per-release-periodic-interval: 6h 24h

Provide any links for context:

See #29387 for more details

This should be done before removing jobs for 1.24

/priority important-soon
/milestone v1.28
cc @kubernetes/release-engineering

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[xmudrii]

/sig release

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale