alamb opened a new pull request #339: URL: https://github.com/apache/arrow-rs/pull/339
# Which issue does this PR close? re https://github.com/apache/arrow-rs/issues/292 # Rationale for this change The idea from the [New Releaes Process Proposal](https://docs.google.com/document/d/1tMQ67iu8XyGGZuj--h9WQYB9inCk6c2sL_4xMTwENGc/edit?ts=60961758) document is to make releases every other week from the `active_release` branch but merge all new code changes to `master` Thus we need a way to port changes that are "safe" for minor and patch releases to the active_release branch # What changes are included in this PR? This PR proposes adding a `cherry-pick-pr.py` script to automate the process of backporting / cherry-picking changes from `master` to `active_release`. # Example I ran this script on a local copy of https://github.com/alamb/arrow-rs with the following commands, which created https://github.com/alamb/arrow-rs/pull/1 ``` git clone [email protected]:alamb/arrow-rs.git /tmp/arrow-rs CHECKOUT_ROOT=/tmp/arrow-rs CHERRY_PICK_SHA=71c21595a0856e4f87838c8c3bb5f2b04fb88024 python3 dev/release/cherry-pick-pr.py ``` # Next steps I plan to run this script as a github action to automatically create proposed cherry-pick PRs for all commits to master. In the interim we can run it manually to create cherry-pick PRs for the `4.1.1` / `4.2.0` release. # Are there any user-facing changes? No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
