-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
create datafusion 6.0.0, ballista 0.6.0 and python 0.4.0 releases #1253
Conversation
I am quite comfortable with the release automation tools and documentation now, I think next time, any committer should be able to run the release so I won't be the only one who is running the releases. |
@@ -18,8 +18,6 @@ | |||
# under the License. | |||
# | |||
|
|||
# point to the old changelog in apache/arrow | |||
front-matter=For older versions, see [apache/arrow/CHANGELOG.md](https://github.com/apache/arrow/blob/master/CHANGELOG.md)\n |
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.
not needed anymore because it's already included in the 5.0.0 changelog and we are appending 6.0.0 changelog on top of it.
Create local release rc tags: | ||
|
||
``` | ||
git tag -f 5.1.0-rc-local | ||
# if there is ballista release | ||
git tag -f ballista-0.5.0-rc-local | ||
# if there is python binding release | ||
git tag -f python-0.3.0-rc-local | ||
``` | ||
|
||
Manully edit the previous release version tag in |
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.
turns out these local tags are not being used at all in changelog automation.
--include-labels "${PROJECT}" \ | ||
--base "${OUTPUT_PATH}" \ |
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 argument appends new version changelog to the existing one file instead of overwriting the full history.
thanks for the update @houqp - i guess i can help with releasing next time (or a minor one, like 6.1) |
Nice work 👍🏻@houqp, looking forward to being a committer and running the release, LOL 😁 |
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 great -- thank you very much @houqp ❤️
Do you plan a release blog? I would love to help make one. There are all sorts of cool things I think we could write about in this release (AVRO support, explain analyze, constant folding, hive partitioning support, and the new roadmap
|
||
**Breaking changes:** | ||
|
||
- Removed deprecated with\_concurrency [\#1200](https://github.com/apache/arrow-datafusion/pull/1200) ([rdettai](https://github.com/rdettai)) |
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.
There is a lot of good stuff in DF 6.0.0 😮
Please go ahead @alamb ! I won't have time to do this until the release has been cut and voted. We can all collaborate to the blog like the last one @andygrove wrote. |
oh by the way after this is cut and release i will help with the homebrew formula update |
Going to wait for @xudong963 's set changes for 6.0.0 release since those PRs look pretty complete and mostly ready to merge :) |
Here is an initial shot: apache/arrow-site#160 I may have missed something |
@houqp Maybe README also need update: https://github.com/apache/arrow-datafusion/blob/master/README.md#using-datafusion-as-a-library
to
|
Thanks @xudong963 for catching that, I have updated the version bump automation to cover |
🎉 |
…ache#1253) * create datafusion 6.0.0, ballista 0.6.0 and python 0.4.0 releases
Rationale for this change
Prepare for the 6.0.0 release.
We have way more changes than I initially expected :D
Also cc @rdettai
What changes are included in this PR?
Are there any user-facing changes?
no