Epic Goal

Engage with Shipwright upstream to cut our next feature release - v0.13.0.

Why is this important?

Upstream first is core value and strategy for adoption. Cutting a release gives customers confidence in the community as well as a reference point for supported features.

Scenarios

• Document upstream features contributed by the community
• Ensure upstream releases can be consumed by the community operator

Acceptance Criteria (Mandatory)

• Upstream release for build controller
• Upstream release for command line (cli)
• Upstream release for operator which deploys v0.13.0

Dependencies (internal and external)

TBD

Previous Work (Optional):

N/A

Open questions::

None

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