jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Phillips <notificati...@github.com>
Subject Re: [jclouds-site] Release Notes for jclouds 1.8.0 (#114)
Date Tue, 05 Aug 2014 07:24:08 GMT
> +* TODO: something about SoftLayer?
> +* TODO: what's new in OpenStack?
> +* TODO: what's new in Rackspace?
> +* This release requires Guava 17.0 and transitions most uses of `InputSupplier` to `ByteSource`.
> +* This is the last version of jclouds to support Java 6. The next major version will
be based on Java 7. If you are still using jclouds on Java 6, please plan accordingly.
> +
> +## <a id="api"></a>API Changes
> +
> +* This release removes or deprecates most uses of Guava `InputSupplier`, including `Strings2.toString`.
 Callers should instead use `ByteSource`, `ByteStreams2.toByteArrayAndClose`, or `Strings2.toStringAndClose`.
 These changes ensure compatibility with future Guava releases.
> +* `BlobStore` introduces a `deleteIfEmpty` method which more accurately matches the
semantics of some providers.  Some providers like Azure have better performance with the existing
`delete` method.
> +* The `resumeNodesMatching`, `suspendNodesMatching` and `rebootNodesMatching` of the
`ComputeService` now return the affected nodes.
> +
> +## <a id="issues"></a>Known Issues
> +
> +* Starting with 1.8.0, the HP Cloud Object Storage provider requires the `region` attribute
to be specified explicitly. This attribute is now used to select the appropriate endpoint.
If the region is not explicitly set, an arbitrary endpoint will be selected, which may differ
from the endpoint chosen when using previous versions of jclouds. See the [provider guide](/guides/hpcloud/)
for an example of how to specify the region.
> +* 1.8.0 includes an incomplete artifact for Google Cloud Storage.  The jclouds team
does not recommend its use and 1.8.1 will either complete support or remove this artifact.

Would this be 2.0.0? 1.8.1, if it comes out, would be a fix version only? Or would we consider
the functional completion of GCS a fix?

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