Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

2016-01-13 Thread Tomaz Muraus
Yeah, need to spin up voting thread and follow the usual release process. Each release artifacts need to be trackable back to the git repo SHA, etc. On Wed, Jan 13, 2016 at 2:06 PM, Eric Johnson wrote: > Hi Tomaz, > > I'll look more closely but I suspect the problem is that Google changed the >

Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

2016-01-13 Thread Eric Johnson
Hi Tomaz, I'll look more closely but I suspect the problem is that Google changed the client id address format (and that is fixed in trunk). Do I need to spin up a vote thread to pull in that single fix? Thanks for flagging this! Eric On Jan 13, 2016 12:52 AM, "Tomaz Muraus" wrote: > Hey Eric,

[dev] Bug in Libcloud 0.20.0 GCE driver?

2016-01-13 Thread Tomaz Muraus
Hey Eric, Are you aware of any bugs in the GCE driver in the latest Libcloud release (0.20.0) - https://twitter.com/gadi_fe/status/686460086361952256 If so, and the fix is already in trunk, feel free to roll out 0.20.1 release with the bug fix. Keep in mind though, that you will probably need to