One thing we forgot to mention, but was discussed at the meetup. The Terremark providers we have code for all don't work as Terremark sunset that api last year I think. This complicates the build, and maintenance, as well feigns support for something that flat doesn't work. The replacement terremark api has no relationship with the old code except being branded by the same company. If someone were to re-introduce terremark, it would need an entire new codebase.
In other words, we should delete the terremark code out of jclouds in version 1.7 -A On Wed, Sep 25, 2013 at 9:47 AM, Adrian Cole <[email protected]>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!) > > 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) > > 1.8 > - Revamp ComputeService to not use futures and instead use Callbacks > - Complete portable volume support > - Look into cancel-ability of blob commands > > 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 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. > > Let's git r done! > -A >
