[SHIP-0038] Use Release Branches for Releasing

shipwright-io / build

Shipwright - a framework for building container images on Kubernetes

https://shipwright.io

Apache License 2.0

654 stars 111 forks source link

[SHIP-0038] Use Release Branches for Releasing #1555

Closed adambkaplan closed 4 months ago

adambkaplan commented 6 months ago

Is there an existing feature request for this?

[X] I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Per SHIP-0038, we are changing our release process to ship official releases from a release branch, rather than from main.

Describe the solution that you would like.

CI and release scripts can be run on a release branch (with release-v* pattern)
Release workflows must use an appropriate release branch and/or git reference (cannot blindly use latest commit from main)

Describe alternatives you have considered.

See SHIP-0038 for discussion

Anything else?

Part of shipwright-io/community#85

adambkaplan commented 5 months ago

@SaschaSchwarze0 @qu1queee Can we call this "done"? I think at this point we just need to cut the official v0.13.0 release for "Build"

qu1queee commented 5 months ago

I would like to fully get a grasp of the whole new process first. Not sure if this is something you can show next Monday during community meeting? .e.g. we need https://github.com/shipwright-io/build/pull/1566 in v0.13.0, how would that work with prow as part of the new process?

adambkaplan commented 4 months ago

/close

We have now release v0.13.0 using the release branch mechanism!

openshift-ci[bot] commented 4 months ago

@adambkaplan: Closing this issue.

In response to [this](https://github.com/shipwright-io/build/issues/1555#issuecomment-2108571791): >/close > >We have now release v0.13.0 using the release branch mechanism! Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.