You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/03 16:50:00 UTC
[jira] [Updated] (ARROW-5077) [Rust] Release process should change
Cargo.toml to use release versions
[ https://issues.apache.org/jira/browse/ARROW-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-5077:
----------------------------------
Labels: pull-request-available (was: )
> [Rust] Release process should change Cargo.toml to use release versions
> -----------------------------------------------------------------------
>
> Key: ARROW-5077
> URL: https://issues.apache.org/jira/browse/ARROW-5077
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Rust
> Affects Versions: 0.13.0
> Reporter: Andy Grove
> Assignee: Yosuke Shiro
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
>
> In the dev tree we use relative path dependencies between arrow, parquet, and datafusion, which means we can't just run cargo publish for each crate from the release source tarball.
> It would be good to have the relaese packaging change the Cargo.toml for parquet and datafusion to have dependencies on a versioned release instead of a relative path to remove this manual step when publishing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)