I'd say there are few significant breaking changes. For dependencies we've kept backwards compatibility on all of them, and other breaking changes shouldn't be a challenge. Apart form that, we've been not backporting issues to 1.9.x for a while with the purpose of releasing 2.0 sooner, so I'd say we should not cut another 1.9.x.
The only issue regarding versions is the Gson 2.7 upgrade [1], but I'd say upgrading is not critical/mandatory. Users can easily shade jclouds with our gson dependency to workaround the issue. I. [1] https://issues.apache.org/jira/browse/JCLOUDS-1160 On 4 October 2016 at 17:23, Andrew Phillips <aphill...@qrmedia.com> wrote: >> I'd say... 2.0 this or next week! :D > > > Nice! Would it make sense to consider a 1.9.2 too, however, for anyone who > needs to stay on that branch? Or are there sufficiently few breaking changes > in 2.x that we feel that's not necessary? > > Regards > > ap
