Skip to content

GH-39761: [Docs] Link to Go documentation references outdated documentation from 2018#39750

Merged
kou merged 8 commits intoapache:mainfrom
gtomitsuka:patch-1
Jan 24, 2024
Merged

GH-39761: [Docs] Link to Go documentation references outdated documentation from 2018#39750
kou merged 8 commits intoapache:mainfrom
gtomitsuka:patch-1

Conversation

@gtomitsuka
Copy link
Copy Markdown
Contributor

@gtomitsuka gtomitsuka commented Jan 22, 2024

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?

  • 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.

Current link references old v1 implementation from 2018 (out-of-date), confusing people on Arrow for Go's capabilities
@gtomitsuka gtomitsuka changed the title MINOR: [DOCS] Link to Go documentation references outdated documentation from 2018 MINOR: [Docs] Link to Go documentation references outdated documentation from 2018 Jan 22, 2024
@kou
Copy link
Copy Markdown
Member

kou commented Jan 22, 2024

If we specify a version statically, we need to update it periodically.
Can we use a URL that refers the latest version?

@gtomitsuka
Copy link
Copy Markdown
Contributor Author

gtomitsuka commented Jan 22, 2024

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 arrow/v16 on arrow/go/README.md, I wasn't sure which version to use as only v15 is tagged but switching to v16 for consistency

@kou
Copy link
Copy Markdown
Member

kou commented Jan 23, 2024

We substitute it in our release process:

pushd "${ARROW_DIR}/go"
find . "(" -name "*.go*" -o -name "go.mod" -o -name README.md ")" -exec sed -i.bak -E -e \
"s|(github\\.com/apache/arrow/go)/v[0-9]+|\1/v${major_version}|g" {} \;
# update parquet writer version
sed -i.bak -E -e \
"s/\"parquet-go version .+\"/\"parquet-go version ${version}\"/" \
parquet/writer_properties.go
sed -i.bak -E -e \
"s/const PkgVersion = \".*/const PkgVersion = \"${version}\"/" \
arrow/doc.go
find . -name "*.bak" -exec rm {} \;
git add .
popd

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?

@gtomitsuka
Copy link
Copy Markdown
Contributor Author

Yep, will do

@gtomitsuka gtomitsuka marked this pull request as draft January 23, 2024 11:31
@gtomitsuka gtomitsuka changed the title MINOR: [Docs] Link to Go documentation references outdated documentation from 2018 GH-39761: [Docs] Link to Go documentation references outdated documentation from 2018 Jan 23, 2024
@github-actions
Copy link
Copy Markdown

⚠️ GitHub issue #39761 has been automatically assigned in GitHub to PR creator.

@gtomitsuka gtomitsuka marked this pull request as ready for review January 23, 2024 11:58
@gtomitsuka
Copy link
Copy Markdown
Contributor Author

Should be fixed now

Copy link
Copy Markdown
Member

@zeroshade zeroshade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this LGTM once the failing dev tests are fixed. Most likely the new diffs need to be added to dev/release/post-11-bump-versions-test.rb as expected diffs

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting review Awaiting review labels Jan 23, 2024
@gtomitsuka
Copy link
Copy Markdown
Contributor Author

Thanks for pointing me in the right direction! I updated dev/release/post-11-bump-versions-test.rb, the tests should pass now

@github-actions github-actions bot added awaiting changes Awaiting changes and removed awaiting merge Awaiting merge labels Jan 23, 2024
@github-actions github-actions bot added awaiting change review Awaiting change review and removed awaiting changes Awaiting changes labels Jan 24, 2024
@gtomitsuka
Copy link
Copy Markdown
Contributor Author

Thanks for the review! I applied all requested changes.

Copy link
Copy Markdown
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Thanks!

@kou kou merged commit 2e8bd8d into apache:main Jan 24, 2024
@kou kou removed the awaiting change review Awaiting change review label Jan 24, 2024
@github-actions github-actions bot added the awaiting merge Awaiting merge label Jan 24, 2024
@conbench-apache-arrow
Copy link
Copy Markdown

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.

dgreiss pushed a commit to dgreiss/arrow that referenced this pull request Feb 19, 2024
…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>
thisisnic pushed a commit that referenced this pull request Mar 8, 2024
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] Link to Go documentation references outdated documentation from 2018

3 participants