I was about to ask something similar. Is there a reason for having a 1.7.4 and a 1.8.0 release? Can't we simply do a 1.8.0 to alleviate the Guava pain and then do a v2.0 release?
Also, IIRC one of the big ticket items in v2.0 was the graduation of the new openstack implementation from jclouds-labs to the main jclouds code. We should probably start that process sooner so that it gets as much testing as possible (and possibly bug fixes). -Shri On Mon, Jun 30, 2014 at 5:10 PM, Andrew Phillips <aphill...@qrmedia.com> wrote: >>> So how about this? > > > My preference would be for 1.8.0 with the latest Guava version, branching > off master, being the next release, and the last to support Java 6. > > 2.0, coming in Sept, would be the first version to support Java 7 and up > only. > > ap
