-
Notifications
You must be signed in to change notification settings - Fork 841
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
Update version to 22.0.0
and update CHANGELOG
#2612
Conversation
22.0.0
22.0.0
and update CHANGELOG
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.
@@ -19,114 +19,110 @@ | |||
|
|||
# Changelog | |||
|
|||
## [21.0.0](https://github.com/apache/arrow-rs/tree/21.0.0) (2022-08-18) |
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.
🤔 something I clearly haven't documented is that I normally copy the old release notes into https://github.com/apache/arrow-rs/blob/master/CHANGELOG-old.md -- is there any chance yuo can do that too (and make a note in the readme?)
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.
Sure! I think we should automate this as well haha.
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.
It would be awesome to do so -- I haven't had the time. Any chance you want to take it on ? Some simple shell script / python would probably be sufficient.
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.
@alamb Yes. That's appropriate for this weekend lol.
@iajoiner thanks again for this PR. I took the liberty of merging up from master to resolve a merge conflict. I have also updated tags on the various tickets. If you get chance to address the feedback on this PR (e.g. restore the old release notes in CHANGELOG-old.md) by tomorrow morning (US Eastern) that would be great. Otherwise no sweat and I'll handle doing it. Thanks |
(I plan to merge this PR tomorrow morning and cut a release candidate) |
@alamb Don’t worry I will take care of that.
…On Thursday, September 1, 2022, Andrew Lamb ***@***.***> wrote:
@iajoiner <https://github.com/iajoiner> thanks again for this PR. I took
the liberty of merging up from master to resolve a merge conflict. I have
also updated tags on the various tickets.
If you get chance to address the feedback on this PR (e.g. restore the old
release notes in CHANGELOG-old.md) by tomorrow morning (US Eastern) that
would be great. Otherwise no sweat and I'll handle doing it.
Thanks
—
Reply to this email directly, view it on GitHub
<#2612 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADPH4IKI47ZSUTBEB3FMVELV4DRWJANCNFSM6AAAAAAQAPTXQA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@alamb We should be good now haha. |
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.
This is looking great -- thank you @iajoiner
I am going to run the changelog generation script one or two more times now to make sure we are totally synchronized with the latest and greatest changes and then I'll merge and cut the release candidate
@@ -69,7 +69,7 @@ git checkout master | |||
git pull | |||
git checkout -b make-release | |||
|
|||
# Move the content of CHANGELOG.md to CHANGELOG-old.md | |||
# Copy the content of CHANGELOG.md to the beginning of CHANGELOG-old.md |
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.
❤️
And now that I think about what I am actually doing maually here, it is mostly moving the component tags like |
Benchmark runs are scheduled for baseline = 2b2c15b and contender = e5b9d05. e5b9d05 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #2542.
Rationale for this change
Prepare for biweekly release
What changes are included in this PR?
parquet
,parquet-derive
,arrow
andarrow-flight
to 22.0.0Are there any user-facing changes?
Yes