-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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-12701: [Website][Release] Include Rust contributors, committers, and commits in release notes #10774
Conversation
a0bfc6b
to
02f07b6
Compare
78064b1
to
7e4fe17
Compare
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.
Looks good, a few comments
Thanks for doing this @thisisnic! Could you also please change how |
Done |
Co-authored-by: Ian Cook <ianmcook@gmail.com>
Co-authored-by: Ian Cook <ianmcook@gmail.com>
Co-authored-by: Ian Cook <ianmcook@gmail.com>
8ec9dda
to
e38b7a0
Compare
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 @thisisnic!
Created a follow-up ticket to port the release note generation to archery at some point: https://issues.apache.org/jira/browse/ARROW-13483 |
Regenerated the release note for 5.0.0 with this patch: apache/arrow-site#131 |
Thanks! @thisisnic there's a problem with the Rust committers; please see https://github.com/apache/arrow-site/pull/131/files#r678709259 |
@thisisnic I manually fixed the problem with the Rust committers and applied the fix in apache/arrow-site#133. So we're OK for the 5.0.0 release and there's no great urgency, but let's fix the problem before we merge this PR. |
@ianmcook Do you remember what you did to get the correct list on this ticket? I've been looking into it but a lot of what I find online is people complaining that they can't find that information after a squash & merge. |
Closing this ancient PR and starting again in a new one |
Note: this PR does not include DataFusion commits because it is not yet clear what release schedule and tagging conventions will be used for the DataFusion repo.