Skip to content

Add Project Roadmap #260

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

Merged
merged 1 commit into from
May 26, 2025
Merged

Add Project Roadmap #260

merged 1 commit into from
May 26, 2025

Conversation

adambkaplan
Copy link
Member

Changes

Adding a separate document to hold project roadmap information. This includes a link to the main GitHub project board we currently use during backlog refinement sessions.

The roadmap also includes a proposed quarterly release schedule for 2025 that aligns with Tekton's anticipated LTS release schedule (+1 month). The anticipated base Kubernetes and Tekton Pipeline versions are listed - these can be subject to change at the discretion of the build sub-project maintainers.

/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 kind/documentation Categorizes issue or PR as related to documentation. label Jan 10, 2025
@pull-request-size pull-request-size bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 10, 2025
Copy link
Member Author

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

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

Adding review suggestions from 2025-01-13 community meeting.

Adding a separate document to hold project roadmap information. This
includes a link to the main GitHub project board we currently use
during backlog refinement sessions.

The roadmap also includes a proposed quarterly release schedule for
2025 that aligns with Tekton's anticipated LTS release schedule (+1
month). The anticipated base Kubernetes and Tekton Pipeline versions
are listed in the `build` sub-project's roadmap. Dates are subject to
change at the discretion of project maintainers.

Signed-off-by: Adam Kaplan <[email protected]>
@adambkaplan
Copy link
Member Author

After some reflection, I decided to move the Kubernetes/Tekton version details to the Build project's roadmap. I also wanted to communicate our intent for the Build project to publish its ".0" release ahead of the overall project release by two weeks. PR with these details is here: shipwright-io/build#1776

@adambkaplan
Copy link
Member Author

@SaschaSchwarze0 @qu1queee is this OK to merge? I've had a few folks ask me questions about our expected Shipwright release dates.

@qu1queee
Copy link
Contributor

@adambkaplan looks ok to me. As long as we can release releases on time.

@adambkaplan
Copy link
Member Author

/approve

Self-approving

Copy link

openshift-ci bot commented May 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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 May 22, 2025
@adambkaplan
Copy link
Member Author

As long as we can release releases on time.

Fair point, and worth emphasizing that the dates here are goals, not hard promises. To quote Stephen Augustus, "we don't owe you anything."

@qu1queee qu1queee merged commit 592c922 into shipwright-io:main May 26, 2025
1 of 2 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. kind/documentation Categorizes issue or PR as related to documentation. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants