In my opinion, the next release should be a 1.9.0, containing the changes that "prepare" jclouds for the next major release. It is a "fix our broken windows" release, as it will ship the complete de-async stuff, it will remove several obsolete providers, and it will promote others.
This is the must-have list (in my opinion) for 1.9.0: * Fix all AWS live tests. (JCLOUDS-462 [1] and JCLOUDS-775 [2]) * Support AWS signature version 4. (JCLOUDS-480 [3]) * Remove the old Swift provider. * Promote the OAuth API. It is now used only by GCE but if I'm not wrong it will be used by the DigitalOcean v2 api too. * Promote Google Compute Engine. - Fix all failing live tests (there are not many). - Remove its SecurityGroupExtension, as the current implementation and how firewalls work in GCE is not aligned with how the SGE works. * Support Docker 1.3.2 (Complete the corresponding PR [4]) * Finish fixing the pom.xml inheritance in all repos. (JCLOUDS-104 [5]) * Study the uses of the Apache HttpClient driver and consider migrating to the OkHttp one. The output of this task should be a plan to upgrade or remove the Apache HC driver. In that release, we should make sure that all live tests pass for the major providers: * AWS * Rackspace * Google * Azureblob (and ideally compute, despite being in labs) Regarding the timing, I think we are not yet in a good position to set a hard (or even soft) date. We'd better first come up with the TODO list, and hopefully distribute the work so we can all work together to make that release happen, even if that means getting out of our comfort area (or comfort providers). Ignasi [1] https://issues.apache.org/jira/browse/JCLOUDS-462 [2] https://issues.apache.org/jira/browse/JCLOUDS-775 [3] https://issues.apache.org/jira/browse/JCLOUDS-480 [4] https://github.com/jclouds/jclouds-labs/pull/113 [5] https://issues.apache.org/jira/browse/JCLOUDS-104 On 8 December 2014 at 21:05, Zack Shoylev <zack.shoy...@rackspace.com> wrote: > I wanted to start a discussion about getting the next release done. Here are > some questions that we should discuss. Feel free to add more (what am I > missing here?). This will also help us get on the same page. > > 1. What is the next release version: 1.8.2, 1.9.0, 2.0.0 ? > > 2. What should be the minimum included in it? > > 3. Can we get a release out by the end of December (considering holidays)? > > Thanks, > Zack