Hi Gulshan We try to not break compatibility, but do encourage collaboration especially around a new client library. If you are able to get the base functionality in place and are working on the additional transports and protocols that is a fine approach. I would recommend you take a look at what occurred for the go library, it is one of our newer libraries and Jens did a great job with it. If you have any questions please feel free to email the dev@ list or join us on irc in #thrift on freenode. Thanks for all the work on adding a new client library, appreciate your efforts in this area
-Jake On Mon, Jun 8, 2015 at 6:09 PM, Gulshan Singh <gsingh2...@gmail.com> wrote: > Hi, I'm working on Rust bindings for Thrift. I was wondering what the > policy is for breaking changes to library APIs, especially for new > languages. Can we have our changes merged but specify that the API is > unstable for a certain amount of time so people can use it and give > feedback, or is everything final after the language is added? >
