Add default .ocm/branch-info.yaml file#442
Merged
petersutter merged 2 commits intomasterfrom Feb 6, 2026
Merged
Conversation
8R0WNI3
requested review from
grolu,
holgerkoser and
petersutter
as code owners
gardener-robot
added
needs/review
|
@holgerkoser, @grolu You have pull request review open invite, please check |
Contributor
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
gardener-robot
added
the
lifecycle/stale
Member
Author
|
/remove-lifecycle stale |
|
@8R0WNI3 Command |
8R0WNI3
removed
the
lifecycle/stale
Contributor
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
gardener-robot
added
the
lifecycle/stale
8R0WNI3
removed
the
lifecycle/stale
Contributor
|
The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
You can:
/lifecycle stale |
gardener-prow
bot
added
the
lifecycle/stale
8R0WNI3
removed
the
lifecycle/stale
gardener-prow
bot
added
the
cla: yes
petersutter
force-pushed
the
8R0WNI3-branch-info
branch
from
7362744 to
1802b30
Compare
petersutter
approved these changes
Feb 6, 2026
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petersutter The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. DetailsGit tree hash: 6799f84bb87a927beebd32f238c0de3bb0c4d92c |
gardener-prow
bot
added
the
approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Introduces the
.ocm/branch-info.yamlfile which is used to collect release-data compatible to the format used by the endoflife.date project. Therefore, thesupported-versions-countas well asrelease-cadenceattributes are used to create an estimated end-of-life date ((estimated) EoL Date = Release Date + supported-versions-count * release-cadence). If there are irregular deviations from this rule, the release information may always be updated manually in the (internal) repository holding the release-data. Thesignificant-partis the version part which is subject of being maintained. In case of questions, please reach out to CICD team.Special notes for your reviewer:
The
.ocm/branch-info.yamlfile this PR introduces only contains the default values. This means, having no explicit branch info file is equivalent to having this file with the default values. Please adjust this PR/the file to reflect the release information which is actually valid for this component.How to categorize this PR?
/area delivery
/kind task
Which issue(s) this PR fixes:
NONE
Release note: