Skip to content
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.

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

Do not automatically backport each PR to stable #549

Merged
merged 1 commit into from
Jan 19, 2022

Conversation

shssoichiro
Copy link
Collaborator

The way we have been doing releases does not coincide well with how we
have been utilizing our stable branch. Given that we release from
master, and that many people in the community use master on a daily
basis, it makes more sense for stable to always match the latest
released version, and for master to include unreleased changes which are
considered "stable".

For experiments, we should instead use a feature branch per experiment
until we are confident that it is ready to be merged into master.

The way we have been doing releases does not coincide well with how we
have been utilizing our stable branch. Given that we release from
master, and that many people in the community use master on a daily
basis, it makes more sense for stable to always match the latest
released version, and for master to include unreleased changes which are
considered "stable".

For experiments, we should instead use a feature branch per experiment
until we are confident that it is ready to be merged into master.
@shssoichiro shssoichiro merged commit e9cb98c into master-of-zen:master Jan 19, 2022
@shssoichiro shssoichiro deleted the backport-rework branch January 19, 2022 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants