Skip to content

Conversation

@8R0WNI3
Copy link
Member

@8R0WNI3 8R0WNI3 commented Oct 28, 2025

What this PR does / why we need it:
Introduces the .ocm/branch-info.yaml file which is used to collect release-data compatible to the format used by the endoflife.date project. Therefore, the supported-versions-count as well as release-cadence attributes 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. The significant-part is 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.yaml file 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:

NONE

@8R0WNI3 8R0WNI3 requested a review from a team as a code owner October 28, 2025 06:57
@gardener-prow gardener-prow bot added area/delivery Delivery related kind/task General task cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 28, 2025
Comment on lines 4 to 5
supported-versions-count: 2
release-cadence: 2w # d (days), w (weeks), y | yr (years)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, please also add a license header.

Suggested change
supported-versions-count: 2
release-cadence: 2w # d (days), w (weeks), y | yr (years)
supported-versions-count: 1
release-cadence: null # d (days), w (weeks), y | yr (years)

@AleksandarSavchev
Copy link
Member

/lgtm
/approve

@gardener-prow gardener-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 12, 2025
@gardener-prow
Copy link

gardener-prow bot commented Nov 12, 2025

LGTM label has been added.

DetailsGit tree hash: e59346ce4d333820919ef54ee6d8a90f43ff3085

@gardener-prow
Copy link

gardener-prow bot commented Nov 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AleksandarSavchev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 12, 2025
@gardener-prow gardener-prow bot merged commit 7a4c014 into main Nov 12, 2025
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/delivery Delivery related cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/task General task lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants