Skip to content
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

doc: 2025 Release Schedule #1776

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

adambkaplan
Copy link
Member

Changes

Update the roadmap to include the tentative release schedule for 2025. This schedule includes the expected versions of Kubernetes and Tekton used for development and CI testing. The dates lead the overall project release schedule by two weeks to encourage updates/rebases in downstream projects, such as the CLI and operator.

/kind documentation

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

Update the roadmap to include the tentative release schedule for 2025.
This schedule includes the expected versions of Kubernetes and Tekton
used for development and CI testing. The dates lead the overall project
release schedule by two weeks to encourage updates/rebases in
downstream projects, such as the CLI and operator.

Signed-off-by: Adam Kaplan <[email protected]>
@openshift-ci openshift-ci bot added the release-note-none Label for when a PR does not need a release note label Jan 14, 2025
@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 14, 2025
@openshift-ci openshift-ci bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jan 14, 2025
Copy link
Contributor

openshift-ci bot commented Jan 14, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from adambkaplan. For more information see the Code Review Process.

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. release-note-none Label for when a PR does not need a release note size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

1 participant