+1 IMHO, trade off is between getting fixes, especially security fixes, and possibility that AWS introduce a tweak that breaks our use case.
The subtlety is that you'd use the latest version before integration testing rather than before release. I.e. get as many fixes as possible, but also make sure we don't ship something broken. Am I splitting hairs? (http://idioms.thefreedictionary.com/split+hairs) DL > -----Original Message----- > From: Prasanna Santhanam [mailto:t...@apache.org] > Sent: 06 July 2013 2:44 PM > To: dev@cloudstack.apache.org > Subject: Re: AWS SDK version for object store > > On Fri, Jul 05, 2013 at 06:27:46PM +0530, Prasanna Santhanam wrote: > > There was another issue I found today with the SDK v1.3.21. It appears > > I can't use periods in the name of a bucket. I see an SSL Exception > > when this is done [1]. The bug is fixed in the v1.3.22. There are also > > couple of other issues fixed related to s3 on the latest version of > > the SDK. Is there any reason not to use the latest stable SDK version > > in CloudStack? IOW, why did we choose the v1.3.21? > > > > [1] http://issues.apache.org/jira/browse/CLOUDSTACK-3374 > > > Fixed by bumping up the version to 1.3.22. But would still like to bump it up > to the latest stable version of the SDK available at the time of the release > ACS > 4.2 > > Thoughts? > > > -- > Prasanna., > > ------------------------ > Powered by BigRock.com
