SHIP-0038: Release Branching and Backports

[adambkaplan]

Changes

Provisional enhancement proposal to outline Shipwright's strategy for release branching and applying backports. The proposal's goal is to let sub-projects issue patch releases for bug fixes and security advisories. This is accomplished using a release branch name convention and updates to project release processes.

Future iterations of this proposal will identify specific changes to be made in our existing release tooling. These updates will also describe how to apply these procedures retroactively to the v0.12.0 releases of the following sub-projects:

• build
• operator
• cli

Relates to #85

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

[qu1queee]

neat, I like the proposed process.

[openshift-ci[bot]]

[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: - ~~[OWNERS](https://github.com/shipwright-io/community/blob/main/OWNERS)~~ [SaschaSchwarze0] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[qu1queee]

/lgtm