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
ARROW-13485: [Release] Replace ${PREVIOUS_RELEASE}.9000 in r/NEWS.md by post-12-bump-versions.sh #10828
Conversation
…mp-versions.sh We need this because we changed to use release branch style.
@@ -121,18 +121,15 @@ update_versions() { | |||
DESCRIPTION | |||
rm -f DESCRIPTION.bak | |||
git add DESCRIPTION | |||
# Replace dev version with release version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's another gap here with regards to patch releases since that version bump goes on top of the previous major release branch. It's fine as long as there is a news entry corresponding to the patch release before the script is run, but if not, this will overwrite the current release version entry. I'm not sure there's a great solution to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't confirm carefully but this will work well by running the following command on maint-X.Y.x
branch after we release X.Y.0:
BUMP_DEFAULT=0 BUMP_VERSION_POST_TAG=1 dev/release/post-12-bump-versions.sh X.Y.0 X.Y.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kou!
@kszucs Do you want to review this? |
I'll merge this. |
…by post-12-bump-versions.sh We need this because we changed to use release branch style. Closes apache#10828 from kou/release-update-version-r Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
We need this because we changed to use release branch style.