Hi Everett, I’m all for capitalizing on an opportunity to promote the project, and I wouldn’t be opposed to moving up the 2.0 release a bit as long as we have some solid updates and new provider offerings to make the release worthy of the 2.0 versioning. My only concerns would be making sure that we have completed the roadmap goals and since 2.0 is largely the same as 1.8, that we have enough time to watch and fix issues that may start to trickle in as users begin using 1.8.
I’m a bit late to the "release cadence” discussion and I probably need to review that thread another time or two, but I may be the only one who is not a fan of attempting scheduled releases of Apache projects. With all of the moving parts and contributors from different companies, all with different levels of availability, and focus, a predictable schedule will be tough to achieve at times, whereas logically laid out feature roadmaps will evolve in a more organic way and help trigger release discussions as the roadmap items are checked off. And of course, the roadmap can and will change based on community discussions. So I’m fine with moving up releases as long as they have the roadmap items agreed upon by the community. Scheduled releases are only going to bring pain, misery, and conflict IMHO. Obviously each project has a different set of dynamics, but this has been my experience on almost all Apache projects I work on :-) -- Chris Custine On August 29, 2014 at 6:51:44 AM, Everett Toews (everett.to...@rackspace.com) wrote: Hi All, At our current release cadence we would reach 2.0.0 until Feb. 2015. I’d like to propose that we release 2.0.0 in mid-Sept. for a number of reasons. 1. A big boost in interest for jclouds at JavaOne I’ll be giving an “Introduction to Apache jclouds” session at JavaOne on Sept. 30. I think we could get a big boost in interest for jclouds if I announce that we’ve gone to 2.0.0 and Java 7. Especially if we follow this up with an ASF press release shortly before or after. 2. Using Java 7 Now that we’ve committed to using Java 7 it would be good to release it too. It would also be nice if we release the Java 7 version of jclouds to our users more than a month before the Java 7 EOL in Apr. 2015. ;) 3. Makes development a bit easier When back porting changes to 2.0.x branch we wouldn’t have to worry about accidentally back porting something that is Java 7 specific like we do with 1.8.x. If people still need 1.8.1 then we can still release 1.8.1 alongside 2.0.0. It terms of dates we could do the following. Code freeze: Sept. 19 Release begins: Sept. 22 Let me know what you think. Thanks, Everett
