ericphanson commented on pull request #278: URL: https://github.com/apache/arrow-julia/pull/278#issuecomment-1019337802
It would be great if this could cover the answer to https://github.com/apache/arrow-julia/pull/267#issuecomment-1019308997 - often when folks contribute a fix or feature they are eager for a release so they can use it downstream. How it used to work is that after most fixes or features (or on request), Arrow.jl would tag a release. This is done by increasing the version number, and asking the JuliaRegistrator bot to make a PR to the General registry of Julia packages, which would be automatically merged if certain checks passed, which would then write a comment on a “tagbot trigger issue” which would trigger the tagbot workflow to generate a git tag and GitHub release. (This process is somewhat convoluted to guarantee that releases are only made after registration is successful, and is standard in the Julia ecosystem). The only manual step in this process is to kick it off. This process also requires the JuliaRegistrator bot is installed on this repository. If that is a big problem, one can use the web UI at juliahub.com (which is run by Julia Computing, not the open source community), or registration PRs can be manually (by hand or with the help of LocalRegistry.jl) made to the General registry, which will require manual merging by a registry maintainer (since such PRs won’t be eligible for automerge, at least at this time). I am not very familiar with Apache’s release process but I am with the Julia ecosystem’s so let me know if anything is unclear or if I can help answer questions or otherwise try to facilitate. -- 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]
