jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Gaul <notificati...@github.com>
Subject Re: [jclouds-site] Post about the 2014-03-04 Meetup (#62)
Date Thu, 06 Mar 2014 18:33:56 GMT
> +
> +Next up was Andrew Gaul from Maginatics with an informative presentation at [0:40 of
the meetup](http://www.youtube.com/watch?v=8nuON0zGVJI&t=40m00s) on [Apache jclouds at
Maginatics](http://gaul.org/talks/jclouds-at-maginatics/). I personally learned a lot from
Andrew's presentation like the wide variety of differences amongst object storage providers.
The engineering work that Gaul and the team from Maginatics have done around the BlobStore
portable API in jclouds is impressive.
> +
> +At [1:09 of the meetup](http://www.youtube.com/watch?v=8nuON0zGVJI&t=69m0s) we made
a toast to Ignasi Barreraā€ˇ for his work in kicking off the jclouds website redesign. Thanks
Ignassi! And thanks to everyone who helped make it a reality!
> +
> +## Discussion
> +
> +Then we had a good talk about the future of jclouds. A few interesting points came out
of the discussion.
> +
> +1. It's time to seriously considering dropping support for Java 6. Java 6 is officialy
end-of-life and has been a security bug ridden mess for Java. It's time to move on. We agreed
on a rough plan of action to move forward.
> +    1. Reach out to users. A blog post dedicated to the topic and sending out an email
and tweets to get user feedback.
> +    1. The last branch to have support for Java 1.6 will be a long lived branch, effectively
indefinite. We will backport crucial bug fixes and do releases on the branch but no new features
will be added to it.
> +    1. The exact timing and releases in which these things happen have yet to be decided
> +1. There was concern expressed by the Maginatics team over the performance impact of
the RestAnnotationProcessor for BlobStore intensive work.
> +    1. In his presentation, Gaul mentioned that Maginatics had discovered that the overhead
of reflection call in the RestAnnotationProcessor were causing what should have been I/O intensive
work to also be CPU bound.
> +    1. The Maginstics team was interested in experimenting with alternatives to the

typo: Maginatics

Reply to this email directly or view it on GitHub:
View raw message