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

Merged
merged 1 commit into from
Jan 31, 2025
Merged

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

@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
- v0.15.0: week of 2025-02-14
- Kubernetes version: 1.32
- Tekton Pipelines version: 0.68-LTS (expected)
Copy link
Member

Choose a reason for hiding this comment

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

Do you have insights into if Tekton changed their scheduling? v0.67 should have been released already but is not. I doubt there will be a 0.68 in the next two weeks therefore.

Copy link
Member Author

Choose a reason for hiding this comment

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

0.67 might be delayed due to some significant infra changes happening on their end. They are moving to use ghcr.io for future releases as a cost saving measure.

Copy link
Member

Choose a reason for hiding this comment

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

I suggest to then state 0.67 here (based on https://tektoncd.slack.com/archives/CLCCEBUMU/p1738001632235419). We probably need to re-check on their future schedule.

Copy link
Member

Choose a reason for hiding this comment

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

Ignore it. Tekton skipped 0.67 and went straight to 0.68 - which is an LTS.

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]>
@SaschaSchwarze0
Copy link
Member

Rebased.

Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 31, 2025
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2025
@adambkaplan
Copy link
Member Author

Going to "red button merge" this since failing tests are unrelated flakes.

@adambkaplan adambkaplan merged commit f062fe0 into shipwright-io:main Jan 31, 2025
15 of 19 checks passed
@adambkaplan adambkaplan deleted the 2025-roadmap branch January 31, 2025 20:41
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. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. 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: Done
Development

Successfully merging this pull request may close these issues.

2 participants