The ElasticHosts changes will definitely need more work, so I'm fine too with starting the release and leave them for the next one
I. On 30 March 2014 20:31, Shrinand Javadekar <[email protected]> wrote: > Bug 510 [1] is fixed on master but I don't think I'll have time to fix > the todo's and test it by Monday morning EDT to make it to 1.7.2. I'm > fine waiting for the next jclouds release for it. Have we decided on > the date for the jclouds 1.8.0 release? > > Also, I'd like to assist with the testing of the RC bits, especially > the blobstore part. Will keep an eye on the mailing list for that. > > Thanks. > -Shri > > [1] https://issues.apache.org/jira/browse/JCLOUDS-510 > > On Sun, Mar 30, 2014 at 7:58 AM, Andrew Phillips <[email protected]> > wrote: >>> 1.7.1 released on 11 February so I propose that we start the 1.7.2 >>> release process the week of 31 March to follow our six week cadence. >>> Does anyone want to volunteer for this release? Currently addressed >>> issues: >>> >>> >>> https://issues.apache.org/jira/browse/JCLOUDS-506?jql=project%20%3D%20JCLOUDS%20AND%20resolution%20%3D%20fixed%20AND%20fixVersion%20%3D%201.7.2 >> >> >> If nobody else is available I should be able to start cutting the release on >> Monday morning EDT. >> >> Do we have all the issues in that we feel urgently need to be included? I >> know Ignasi was interested in getting some ElasticHosts changes in, but from >> what I understand that PR needs some more work... >> >> ap
