-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
GH-43878: [Go][Release] Remove Go related codes from our release scripts #44172
Conversation
|
@zeroshade will we have to update these urls to point here Line 107 in 18319d3
Line 79 in 18319d3
Is there any way to point to latest so we don't have to bump the release on arrow when we release arrow-go? |
@github-actions crossbow submit verify-rc-source-* |
Revision: 42dd7f3 Submitted crossbow builds: ursacomputing/crossbow @ actions-61cfbe58a4 |
Ubuntu 20.04 issues are unrelated: |
How about creating https://arrow.apache.org/go/ as the canonical Apache Arrow Go website? |
How can I do this? @kou |
We can use
With the |
@kou are you ok for me merging this? The docs, once deployed with the release, will point to |
Yes! |
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.
👍
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit aee3078. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 3 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
The Go implementation is moving to apache/arrow-go from go/ in apache/arrow.
What changes are included in this PR?
Remove go related release scripts from apache/arrow
Are these changes tested?
The source verification is tested via archery
Are there any user-facing changes?
Yes, Go will not be releases as part of Apache Arrow anymore.