Sorry, without a show-stopper or regression issue, we will continue with 1.6.3 as-is. This release stretched beyond jclouds usual six-week cadence due to graduation from the incubator and we can address further issues in 1.6.4 or 1.7.0. I appreciate that a commit missing a given release inconveniences some users but believe that this argues for more *releases* not more release *candidates*.
On Thu, Nov 28, 2013 at 06:45:39PM +0000, Alex Heneveld wrote: > > Thanks Andrew P. > > Sorry for posting to the wrong thread. There is something funny in how > [THREAD] prefixes are getting ignored (just mentioning in case anyone else > has that) somewhere between Thunderbird and Google Mail. > > I've also backported the oauth live tests fix at [4] fixing live test > failures with 1.6.3-rc2. > > Between this and the copyright normalisation maybe an rc3 argument can be > made after all! :) > > Best > Alex > > > [4] https://github.com/jclouds/jclouds-labs/pull/42 > > > On 28/11/2013 15:30, Andrew Phillips wrote: > >Moving Alex Heneveld's question to the [DISCUSS] thread... > > > >"Hi folks- > > > >The GCE identity parse fix ([2] and [3]) did not get backported. This will > >cause problems for many users of GCE. > > > >I've created a PR for this backport now at [1]. > > > >Would it be possible to cut a new RC for 1.6.3 including this? I know > >it's work but GCE is the fastest cloud that I've come across so it would > >be nice to have! (Good news is that testing with other clouds all is > >good, including the recent changes to Softlayer.) > > > >Best > >Alex > > > > > >[1] https://github.com/jclouds/jclouds-labs/pull/42 > >[2] https://issues.apache.org/jira/browse/JCLOUDS-362 > >[3] https://issues.apache.org/jira/browse/JCLOUDS-289"; -- Andrew Gaul http://gaul.org/
