Document known limitations for Whirr 0.6.0

Details

Description

We've got some remaining (not critical) issues in the current trunk that will become the branch for Apache Whirr 0.6.0. I believe we should document them and move forward with the release process because at the same time we have a lot of improvements from 0.5.0.

I think the communication about BlobCache unnecessarily focused on the error rather than the constraint, which can scare users. I think we should adjust the language to be in line with the other 2 constraints noted.

Ex.

<li>The "jclouds.aws-s3.endpoint" property is needed in order to use BlobCache with Amazon AWS in a region besides us-east-1. See <a href="https://issues.apache.org/jira/browse/WHIRR-349#comment-13084590">WHIRR-349</a> for a more details</li>.

Adrian Cole (Inactive)
added a comment - 18/Aug/11 18:25 I think the communication about BlobCache unnecessarily focused on the error rather than the constraint, which can scare users. I think we should adjust the language to be in line with the other 2 constraints noted.
Ex.
<li>The "jclouds.aws-s3.endpoint" property is needed in order to use BlobCache with Amazon AWS in a region besides us-east-1. See <a href="https://issues.apache.org/jira/browse/WHIRR-349#comment-13084590"> WHIRR-349 </a> for a more details</li>.

Andrei Savu
added a comment - 18/Aug/11 04:56 I'm marking this as fixed. The link to the JIRA comment explaining the workaround should be good enough and otherwise we should be able to provide assistance on the email list.