-
Epic
-
Resolution: Done
-
Major
-
None
-
builds-1.5
-
Shipwright v0.16
-
False
-
-
False
-
Green
-
Done
-
SECFLOWOTL-237 - CY 2025 Shipwright Release Cadence
-
0% To Do, 0% In Progress, 100% Done
-
With this update, {builds-title} deploys Shipwright v0.16 components.
-
Feature
Epic Goal
Shipwright v0.16 upstream work.
Why is this important?
- Ensure upstream community releases on a predictable cadence.
Scenarios
- Tekton rebases
- Kubernetes rebases
- Upstream contributions from community.
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
Who |
What |
Reference |
DEV | Upstream roadmap issue | https://github.com/shipwright-io/community/issues/266 |
DEV | Upstream code and tests merged | https://github.com/shipwright-io/build/pull/1859 https://github.com/shipwright-io/cli/pull/323 https://github.com/shipwright-io/operator/pull/260 |
DEV | Downstream code and tests merged | <link to meaningful PR or GitHub Issue> |
QE | Automated tests merged | <link or reference to automated tests> |
DOC | Downstream documentation merged | <link to meaningful PR> |
DEV | Technical Enablement (slides, demos) prepared | <link to presentation, videos> |
- clones
-
BUILD-1298 Shipwright v0.15
-
- Closed
-
- is cloned by
-
BUILD-1307 Shipwright v0.17
-
- In Progress
-