thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James E. King III (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (THRIFT-4665) Keep Rust library up-to-date on crates.io
Date Mon, 12 Nov 2018 13:02:00 GMT

    [ https://issues.apache.org/jira/browse/THRIFT-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683772#comment-16683772
] 

James E. King III commented on THRIFT-4665:
-------------------------------------------

Typically once 0.12.0 is released, you would generate a build from the 0.12.0 tag and push
it upstream.  This is what I do for perl, for example.  I will be adding dlang/dub as well.
 We will be adding both a "0.12.0" tag and a "v0.12.0" tag to satisfy package managers that
need the "v" prefix (even though it is NOT SemVer compliant, some language package managers
like dlang and go require it).

> Keep Rust library up-to-date on crates.io
> -----------------------------------------
>
>                 Key: THRIFT-4665
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4665
>             Project: Thrift
>          Issue Type: Wish
>          Components: Rust - Library
>    Affects Versions: 0.11.0
>            Reporter: J W
>            Priority: Minor
>
> [https://crates.io/crates/thrift]
> The most recent crate listed is `0.0.4`, which corresponds to thrift `0.10.0` as far
as I can tell.
> Would be nice if the crate was up to date and matched the thrift version.  So, the current
crate would be `0.11.0` and the upcoming crate would be `0.12.0`.
> It will obviously be a problem if the crate version needs to get bumped to `0.11.1` when
no such version of thrift exists.  But at least the MINOR versions match, and that seems
preferable to mapping the seeming unrelated `0.0.4` to `0.10.0`.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message