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

x/build/cmd/relui: add a workflow for doing cherry-picks #65435

Open
dmitshur opened this issue Feb 1, 2024 · 0 comments
Open

x/build/cmd/relui: add a workflow for doing cherry-picks #65435

dmitshur opened this issue Feb 1, 2024 · 0 comments
Labels
Builders x/build issues (builders, bots, dashboards) FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@dmitshur
Copy link
Contributor

dmitshur commented Feb 1, 2024

The minor release process involves creating cherry picks using the process documented at:

https://go.dev/wiki/MinorReleases#making-cherry-pick-cls

As recently suggested by @rsc, there's room to create a relui workflow that can be used to short-circuit the manual steps involved. It probably doesn't need to worry about fully handling unusual cases, or when merge conflicts are involved, but those are relatively rare.

Also relevant is CL 559295 (CC @rolandshoemaker) that does this for publishing private golang.org/x fixes (issue #65756).

@dmitshur dmitshur added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. FeatureRequest labels Feb 1, 2024
@dmitshur dmitshur added this to the Unreleased milestone Feb 1, 2024
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders x/build issues (builders, bots, dashboards) FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Planned
Development

No branches or pull requests

2 participants