What Sebastien has said - if you think there is a need, you can start working on 0.17.1 release.
Depending on what changes have accumulated in trunk so far (backward incompatible changes vs bug fixes), we might want to create 0.17.x branch and only apply this and other bug-fixes top of that branch and base 0.17.1 release from that branch. On Sat, Feb 28, 2015 at 7:57 PM, Eric Johnson <[email protected]> wrote: > On Sat, Feb 28, 2015 at 10:27 AM, sebgoa <[email protected]> wrote: > > > > > On Feb 28, 2015, at 6:45 PM, Eric Johnson <[email protected]> wrote: > > > > > It looks like https://github.com/apache/libcloud/pull/448 was worse > > than I > > > thought. I'm updating Saltstack (built on libcloud) and salt is broken > > with > > > 0.17.0 because of the bug, preventing users from creating GCE VMs. > > > > > > I wanted to raise awareness that if we're accumulating reasons for a > bug > > > fix release, this should count. > > > > > > > Eric in the past we have released bug fixed release very quickly. > > If this is really as bad as it sounds, we can release 0.1.7.1 right away > > (as fast as we can vote) > > As long as you are sure the fix is in works. > > > > > Thanks Sebastian, that's great to hear. I've tested with both Salt and > Ansible, so I'm confident the fix is solid. > > FWIW, I've started to beef up the gce_demo.py > <https://github.com/apache/libcloud/blob/trunk/demos/gce_demo.py> script > to > function as code-samples and live tests since I don't (yet) have a good > mechanism for generating a whole new set of fixtures > < > https://github.com/apache/libcloud/tree/trunk/libcloud/test/compute/fixtures/gce > >. > The next step is to build on that and run live tests with Salt / Ansible > against my dev environment before merging libcloud commits. >
