You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andrew Lamb (Jira)" <ji...@apache.org> on 2021/04/26 12:52:00 UTC
[jira] [Commented] (ARROW-12445) [Rust] Design and implement
packaging process to bundle Rust in signed tar
[ https://issues.apache.org/jira/browse/ARROW-12445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332245#comment-17332245 ]
Andrew Lamb commented on ARROW-12445:
-------------------------------------
Migrated to github: https://github.com/apache/arrow-rs/issues/212
> [Rust] Design and implement packaging process to bundle Rust in signed tar
> --------------------------------------------------------------------------
>
> Key: ARROW-12445
> URL: https://issues.apache.org/jira/browse/ARROW-12445
> Project: Apache Arrow
> Issue Type: Task
> Components: Rust
> Affects Versions: 5.0.0
> Reporter: Jorge Leitão
> Priority: Blocker
> Fix For: 5.0.0
>
>
> 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 message was sent by Atlassian Jira
(v8.3.4#803005)