[FEATURE] Establish a release cadence based on Tekton LTS releases
Opened this issue · 3 comments
Is there an existing feature request for this?
- I have searched the existing feature requests
Is your feature request related to a problem or use-case? Please describe.
Use case.
Describe the solution that you would like.
Tekton provides LTS releases. We can align our cadence to happen after each LTS release(every 3 months). Our releases should come with a bump on the Tekton dependency, towards their latest LTS release.
Describe alternatives you have considered.
None
Anything else?
See https://github.com/tektoncd/pipeline/blob/main/releases.md#release-frequency
Using past history as our guide, we expect Tekton to declare v0.62 as the next LTS with a release date on or around 2024-07-25. Tekon v0.50 will then reach end of life. Key question regarding support:
- Do we keep Shipwright on the "oldest" supported Tekton LTS? If so, how do we ensure Shipwright works on the newest Tekton?
- Do we fast forward Shipwright and use the "newest" Tekton LTS? If so, how do we ensure Shipwright works on older Tekton LTS versions?
From community meeting: we will use the newest Tekton LTS (and k8s) for updating dependencies. We will experiment adding maxtrix testing on older Tekton + k8s in pull requests.
From refinement, to document the conclusion on the cadence, whats being done today as part of this in terms of automation. Doc should be done before closing this Issue.