ARROW-16654: [Dev][Archery] Support cherry-picking for major releases #13230
Conversation
|
|
| return [] | ||
|
|
||
| commit_range = "{}..{}".format(lower, upper) | ||
| commit_range = f"{lower}..{upper}" |
There was a problem hiding this comment.
I love the f-string changes. Thanks!
| if not dry_run: | ||
| release.cherry_pick_commits(recreate_branch=recreate) |
There was a problem hiding this comment.
How about moving dry_run mode implementation to Release?
| if not dry_run: | |
| release.cherry_pick_commits(recreate_branch=recreate) | |
| release.cherry_pick_commits(recreate_branch=recreate, dry_run=dry_run) |
Release knows what git command lines should be ran. If we move dry_run mode implementation to Release, we can implement dry_run mode and non dry_run mode nearby.
There was a problem hiding this comment.
Good idea, but may handle it in follow-up PR.
|
Benchmark runs are scheduled for baseline = 0066e0e and contender = 02af333. 02af333 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Run the following to see what would happens without executing it:
Try creating a
maint-9.0.0branch based off of themasterbranch:Now there should be the
maint-9.0.0branch checked out locally. Rerunning the previous command with--continueoption would do nothing since there are no new commits to apply:So simulate new commits be resetting
maint-9.0.0branch to three commits before the current master:Apply the new patches: