kou commented on PR #45963:
URL: https://github.com/apache/arrow/pull/45963#issuecomment-2764766360
> How many files will this end up being?
By this PR? Or by all related PRs such as #45962 and #45964?
This PR adds 3 files: `docs.tar.gz{,.asc,.sha512}`
All related PRs: 180:
```
3 [1 [source archive] * 3 [original + .asc + .sha512]] +
3 [1 [.mltbx] * 3 [original + .asc + .sha512]] +
126 [(1 [sdist] + 41 [wheels]) * 3 [original + .asc + .sha512])] +
45 [8 [(3 [for Linux] + 4 [for macOS] + 1 [for Windows]) * 3 [original +
.asc + .sha512])] +
3 [1 [docs.tar.gz] * 3 [original + .asc + .sha512]]
```
FYI: #45470 adds more wheels.
> Having the wheels and such be part of the github release makes sense,
people are expecting that if they are not used to ASF ways.
The "people" refers Python users, right? In general, Python users use PyPI
not GitHub Release.
> I think artifacts would be a more appropriate storage for this and are
easily manipulated using `gh`.
If we use GitHub Actions workflow artifacts, people who verify an RC need
their GitHub token to download artifacts from GitHub Actions workflow artifacts.
BTW, we need to use multiple `gh` commands to download from GitHub Actions
wokflow artifacts (`gh workflow list` and `gh run download`). We can use one
`gh release download` command or just `curl` with GitHub Release.
> Or should we create a workflow in arrow-site that uses the released
binaries to build the docs?
It's an option but it's a bit risky. Building docs in a workflow in
arrow-site may be failed after a vote...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
