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

Reply via email to