I do not think we should perform clean-up tasks in minor releases, especially breaking ones, even in labs. Of course on master this is a desired and valuable change which recognizes the GCE as a high-quality and blessed provider. I also do not think we should delay releases for anything other than regressions -- we will have another minor release soon enough.
On Fri, Oct 03, 2014 at 09:36:54AM -0600, Chris Custine wrote: > I suppose this is a good opportunity to discuss gce and oauth > (https://issues.apache.org/jira/browse/JCLOUDS-172). > > There was some debate over whether we should graduate labs projects in a > patch release such as 1.8.1 (comments on JCLOUDS-172), but it seems like most > everyone is ok with it and I want to make sure that this topic gets resolved. > > On the other hand, there have been some issues with GCE API in the last few > weeks which have cast some doubt on graduating from labs right now. I think > they are rather minor issues, but the versioned GCE API changing from the > docs and previous return data makes this worthy of a discussion. > > For my 2 cents, I would say that fixing these issues, merging some stale PRs, > and releasing this in jclouds 1.8.1 on Monday is pushing my sensibility. If > we were to hold off on the release another week or so, my comfort level would > be much better. I’m not arguing to push back the release at all, just > putting out the options. > > Thoughts? > > Thanks, > Chris > -- > Chris Custine > > > On October 2, 2014 at 10:12:29 AM, Everett Toews > (everett.to...@rackspace.com) wrote: > > Let's schedule the release of 1.8.1. > > All code into 1.8.x by Monday, Oct. 6 EOD > Begin release on Tuesday, Oct. 7 > > Can someone volunteer to do the actual release steps? > > I'll be catching up with work stuff all next week after being on the road for > a few weeks but I can do it if necessary. > > Thanks, > Everett > -- Andrew Gaul http://gaul.org/
