kou commented on pull request #278:
URL: https://github.com/apache/arrow-julia/pull/278#issuecomment-1019494122


   We can use `JuliaRegistries/TagBot` action because it's added to allow list: 
See #273 and the linked Jira issue for details.
   
   We need a vote for each new release before we publish a new release. It 
requires the followings:
   
   1. We need to create a source package such as `arrow-julia-x.y.z.tar.gz` for 
each release.
   2. We need to sign the created source package.
   3. (If we have binary packages, we also sign binary packages.)
   4. We need to upload the created source package, (binary packages), sign and 
checksums to https://dist.apache.org/repos/dist/dev/arrow/ or 
https://apache.jfrog.io/ui/native/arrow/ for vote.
   5. We need to at least 3 positive votes (+1) from PMC members (see 
https://arrow.apache.org/committers/ for the current PMC members) to pass the 
release vote.
   6. Release votes SHOULD remain open for at least 72 hours. (This is for 
accepting votes from all time zones.)  
   
   See https://www.apache.org/legal/release-policy.html for details.
   
   Notes:
   
   1. We should prepare verification scripts to verify the release artifacts 
(source package, binary packages, sign and checksums) for voting by PMC 
members. e.g. 
https://github.com/apache/arrow-rs/blob/master/dev/release/verify-release-candidate.sh
   2. It's better that Apache Arrow PMC has at least 3 members who work on 
Apache Arrow Julia for smooth vote in the future.
   
   We can use the standard Julia package release process after a release vote 
is passed. (We also need to publish passed release artifacts in 
https://dist.apache.org/repos/dist/dev/arrow/ to 
https://dist.apache.org/repos/dist/release/arrow/ .)
   
   Here are questions:
   
   1. Do we build binary packages?
   2. @ericphanson Are you interested in joining Apache Arrow PMC in the future?


-- 
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]


Reply via email to