[
https://issues.apache.org/jira/browse/THRIFT-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683675#comment-16683675
]
Allen George commented on THRIFT-4665:
--------------------------------------
[nods]
TL;DR: that's the plan :)
TBH, this happened because I wasn't sure how packages were updated on
crates.io. I thought that the thrift deb builder would do it, but that's not
the case: individual language maintainers do it (and I found this out fairly
recently). Since 0.12.0 was already in the works at that time I figured I'd
wait until it showed up and then bumped the version.
> 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)
