alamb opened a new issue #212: URL: https://github.com/apache/arrow-rs/issues/212
*Note*: migrated from original JIRA: https://issues.apache.org/jira/browse/ARROW-12445 The goal of this task is to agree on the strategy and process, and implement it in dev/release , to bundle Rust's source code on the signed tar as part of the arrow release. Ideas: 1. use the latest published source code in crates.io 2. use a git ref from arrow-rs pointing to the latest release 3. use the source in arrow-rs@master Some pros and cons: 1. * [pro] is is downloaded from within ASF * [pro] it has been released (as it was voted on) * [con] it is not integration-tested against latest arrow@master, only master at the time of the release 2. * [pro] it has been officially released (as it was voted on) * [con] is is downloaded from outside ASF * [con] it is not integration-tested against latest arrow@master, only master at the time of the release 3. * [pro] It is the latest * [pro] it is integration-tested against latest master * [con] it has not been released in crates.io -- 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. For queries about this service, please contact Infrastructure at: [email protected]
