chore: Publish docs

[kou]

What's Changed

Build docs by CI and:

Push an RC tag:

• Upload the built docs to GitHub Releases

Push a release tag:

• Publish the uploaded docs to https://arrow.apache.org/js/{current,${VERSION}} via the asf-site branch

Push to main in apache/arrow-js:

• Publish the uploaded docs to https://arrow.apache.org/js/main via the asf-site branch

Push to non main in apache/arrow-js:

• Do nothing

Push to foks:

• Upload the built docs to GitHub Pages via the gh-pages branch for preview
  • Example: https://kou.github.io/arrow-js/
  • Developers need to enable GitHub Pages explicitly at https://github.com/kou/arrow-js/settings/pages

Closes #10.

[kou]

RC example: https://github.com/kou/arrow-js/releases/tag/v20.0.0-rc3
Release example: https://github.com/kou/arrow-js/releases/tag/v20.0.0
asf-site example: https://github.com/kou/arrow-js/tree/asf-site

[raulcd]

@kou are those scripts and workflows based on any other of our repos or is this process completely different? I am currently losing track on how we do things on others. I tried to understand what was going on with the different branches / directories / forks and really got it when I read the description of the PR. It seems quite important to understand the process, should we add something similar to the PR description to the documentation?

In general looks good to me, I am just slightly concerned whether we will be able to remember what was going on with the different branches/folders/workflows once we have to update it in the future.

[kou]

are those scripts and workflows based on any other of our repos or is this process completely different?

These implementations are completely different from others.
Documentation URL style (`/js/{main,current,${version}/') is same as ADBC's one.

apache/arrow-adbc and apache/arrow-nanoarrow are only automate documentation publishing.
(apache/arrow also automates dev documentation publishing but apache/arrow uses separated apache/arrow-site repo. So it's not done in each commit of main in apache/arrow.)

apache/arrow-adbc nor apache/arrow-nanoarrow don't support preview by GitHub Pages on fork. So apache/arrow-js implementation is (a bit?) more complex than them.

I am currently losing track on how we do things on others. I tried to understand what was going on with the different branches / directories / forks and really got it when I read the description of the PR. It seems quite important to understand the process, should we add something similar to the PR description to the documentation?

Good point. I'll add dev/release/docs.md. I don't want to add it to dev/release/README.md. I want to keep dev/release/README.md just about our release process.

[raulcd]

Good point. I'll add dev/release/docs.md. I don't want to add it to dev/release/README.md. I want to keep dev/release/README.md just about our release process.

Thanks, I think this will be helpful in the future.

[kou]

How about this?
https://github.com/kou/arrow-js/blob/docs/dev/release/docs.md

[raulcd]

LGTM just a couple of nits

[raulcd]

asf-site has been correctly generated:
fb0a5b3