New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change CI and release process to use release branches #347

Closed

jgiannuzzi opened this issue Sep 19, 2023 · 0 comments · Fixed by #452

Assignees

Member

jgiannuzzi commented Sep 19, 2023 •

edited

Loading

We should update our release process to follow this pattern:

All development is done as pull requests against main
main is not expected to be stable
Stable releases are delivered to end users from a release branch (one per minor release, e.g. release/0.3), which is tagged at each release (e.g. v0.3.5)
The release branch is updated via pull requests against it, which are backports ("cherry picks") from main
CI and branch protections need to apply to both main and release/* branches

The text was updated successfully, but these errors were encountered:

jgiannuzzi self-assigned this

jgiannuzzi linked a pull request

that will close this issue

Change CI release logic #452

Merged

4 tasks

jgiannuzzi closed this as completed in #452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment