On Wed, Sep 25, 2013 at 09:47:17AM -0700, Adrian Cole wrote: > From memory, and feel free to add. We discussed many things, focusing most > on releases and completing tasks. > > 1.6.3 > - Andrew Gaul will lead this release and perform it after graduation > (hence no more -incubating in the version!)
Hat trick; three Andrew releases in a row! > 1.7 > - Complete de-futuring core, and removal of deprecated interfaces like > BlobMap. > - Retain AsyncBlobStore for another release until we introduce alternate, > callback style, blob commands. > - Complete portable security groups > - Expose means to deal with multi-region blobstores, (ex. all openstack > swift) For 1.7, I will also improve the out-of-box experience for generic S3, at least disabling virtual host buckets by default and refreshing the S3 provider guide. I have other notes on ecloud, openstack-nova vs. cloudservers, and new Swift backend. > 1.8 > - Revamp ComputeService to not use futures and instead use Callbacks > - Complete portable volume support > - Look into cancel-ability of blob commands We did not complete this discussion, but we should revisit the Java 6 minimum requirement in jclouds 1.8. Perhaps we could use some data-driven approach; could someone at Rackspace share statistics on their User Agent strings? We also must investigate how a Java 7 dependency would affect our downstream projects. > 2.0 > - Cleanup dev process, and look into ways to generate domain classes > - Investigate better use of things like checkstyle and errorprone to > reduce development errors > - Support SPDY/HTTP 2.0 apis We also discussed live test cleanup. I have made progress on this for blobstore and hope that 1.6.3 live tests will pass across all major providers. We need champions for compute to do the same to give us more confidence in the release process. > We all decided that it is up to us to complete the tasks of 1.7, including > facilitating change through pull reviews, and not re-hashing discussions > about things already discussed and deprecated. There's a lot of code to > touch now (in 1.7), but it will make 1.8+ far easier to implement. If we > cannot rally the full list of changes for 1.7, we'll group them into what > can be pushed out now vs 1.8. I attached a photo of our whiteboard talk. Note that we completed only 70% of the Andrew discussion and important topics like werewolves remain unexplored. -- Andrew Gaul http://gaul.org/
