GH-39761: [Docs] Link to Go documentation references outdated documentation from 2018#39750
GH-39761: [Docs] Link to Go documentation references outdated documentation from 2018#39750kou merged 8 commits intoapache:mainfrom
Conversation
Current link references old v1 implementation from 2018 (out-of-date), confusing people on Arrow for Go's capabilities
|
If we specify a version statically, we need to update it periodically. |
|
I've researched this and haven't found any way to tag a version as latest on godoc; I checked the codebase it seems that the team is already aware of this issue and uses the static link to |
|
We substitute it in our release process: arrow/dev/release/utils-prepare.sh Lines 152 to 165 in c9ca62a If we need it, could you open a new issue (this is not a MINOR fix https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes ) and use the same approach in this PR? |
|
Yep, will do |
|
|
|
Should be fixed now |
|
Thanks for pointing me in the right direction! I updated |
|
Thanks for the review! I applied all requested changes. |
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 2e8bd8d. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
…ocumentation from 2018 (apache#39750) ### Rationale for this change The godoc format shows docs in a versioned fashion, making the ["basic" link](https://pkg.go.dev/github.com/apache/arrow/go) reference v0.0.0 from 2018, and godoc doesn't warn you when docs are outdated. Accordingly, for people to find "real" documentation, they have to manually search for the latest docs. Otherwise, it gives the impression that the package is abandoned / makes devs waste considerable time — e.g., I work with Go professionally and wasted 15 minutes on the 2018 docs until I realized they were wrong. ### What changes are included in this PR? * Reference the latest version (v16) in the list of supported implementations of the Arrow website & R package. * Add step to release process that automatically updates the version on release ### Are these changes tested? Yes, I've added tests for this to `dev/release/post-11-bump-versions-test.rb`. ### Are there any user-facing changes? Yes, the link to Implementations > Go on the website will change. * Closes: apache#39761 Authored-by: Gabriel Tomitsuka <g@gtomitsuka.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
…tation from 2018 (#39750) ### Rationale for this change The godoc format shows docs in a versioned fashion, making the ["basic" link](https://pkg.go.dev/github.com/apache/arrow/go) reference v0.0.0 from 2018, and godoc doesn't warn you when docs are outdated. Accordingly, for people to find "real" documentation, they have to manually search for the latest docs. Otherwise, it gives the impression that the package is abandoned / makes devs waste considerable time — e.g., I work with Go professionally and wasted 15 minutes on the 2018 docs until I realized they were wrong. ### What changes are included in this PR? * Reference the latest version (v16) in the list of supported implementations of the Arrow website & R package. * Add step to release process that automatically updates the version on release ### Are these changes tested? Yes, I've added tests for this to `dev/release/post-11-bump-versions-test.rb`. ### Are there any user-facing changes? Yes, the link to Implementations > Go on the website will change. * Closes: #39761 Authored-by: Gabriel Tomitsuka <g@gtomitsuka.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Rationale for this change
The godoc format shows docs in a versioned fashion, making the "basic" link reference v0.0.0 from 2018, and godoc doesn't warn you when docs are outdated. Accordingly, for people to find "real" documentation, they have to manually search for the latest docs.
Otherwise, it gives the impression that the package is abandoned / makes devs waste considerable time — e.g., I work with Go professionally and wasted 15 minutes on the 2018 docs until I realized they were wrong.
What changes are included in this PR?
Are these changes tested?
Yes, I've added tests for this to
dev/release/post-11-bump-versions-test.rb.Are there any user-facing changes?
Yes, the link to Implementations > Go on the website will change.