Ignasi, I think Packet can be promoted as well: API are quite clean and we have the account for the live testing.
I'd like to fix jclouds-karaf (namely having https://github.com/jclouds/jclouds-karaf/pull/92) before the release. Otherwise no strong objections! Thanks, Andrea On Wed, Feb 15, 2017 at 5:15 PM, Zack Shoylev <zack.shoy...@rackspace.com> wrote: > +1 > ________________________________________ > From: Ignasi Barrera <n...@apache.org> > Sent: Wednesday, February 15, 2017 3:37 AM > To: dev@jclouds.apache.org > Subject: Time to release jclouds 2.0.1 > > Hi! > > I'd like to propose to release jclouds 2.0.1. There have been several > bugfixes and many improvements to our Azure ARM provider, including > the implementation of the security group features and their load > balancer API. We have also added the Packet (bare metal in the cloud) > and Vagrant providers in labs. > > All three providers are in a very good shape, and at least ARM and > vagrant are in a state that I'd say they could be promoted. However, > I'd like to have this release first so users can start testing them > and giving feedback, > > WDYT? > > If there are no objections, I'll volunteer to cut the release in a day or > two. > > > > I. >
