A modern programming language that makes developers happier.

kotlinlang

&gt;&gt;&gt; A first question, ElasticSearch REST API tends to be more API compatible than the binary, although both are getting better within their semantic version ranges.  But, it may not always be true, and it is possible that you would have two versions of ElasticSearch running at the same time in two clusters.  So is it useful for us to have two versions of the library, one that has versioning in the package naming, and another that is always just “current”?  Therefore you could have `uy.kohesive.estatik.v2_0_x.Something` or `uy.kohesive.estatik.v2_x.Something`  and at the same time an equivalent `uy.kohesive.estatik.Something` or `uy.kohesive.estatik.latest.Something` or ?  what is a good naming strategy so you can support two versions with confidence (i.e. 1.x vs. 2.x will be common for a while for some people)