Very close. The Microsoft guys have a branch where the base live tests are passing, and that's enough even to promote the provider. They have to do some cleanups though, but everything is in place, so it would not take much.
This said, I also see value in a 1.9.3 release: as you say it's been over a year since 1.9, but 2.0 will introduce some important changes and I'm not sure everyone would be able to upgrade. There are many issues that are only in 2.0 that could be cherry-picked to 1.9.x that could justify a 1.9.3 release. In the end... I don't see anything wrong in releasing 1.9.3, even if we release it the same day than 2.0. It is all about providing the users what they need. I'd say +1 to release 2.0 as soon as B2 and ARM are complete (and I'd promote Docker too). And +1 to release 1.9.3. I volunteer to scan the JIRA (although I'd appreciate help on this) looking for issues affecting 1.9.2 that are only in 2.0 and see which ones can be cherry-picked. Then I'll volunteer to do the release too. On 17 June 2016 at 22:31, Andrew Gaul <g...@apache.org> wrote: > I strongly prefer to run a 2.0 release from master; it has been over a > year since 1.9! ASAP is always better, but we have the B2 and Azure ARM > providers under development. The former is almost complete; how close > are we on the latter? > > On Fri, Jun 17, 2016 at 02:36:21AM +0200, Andrew Phillips wrote: >> Hi all >> >> I've created a skeleton wiki page for the upcoming board report: >> >> https://cwiki.apache.org/confluence/display/JCLOUDS/2016+-+July+Board+Report+Draft >> >> There's a bunch of TODOs in there, so please update/amend as >> appropriate. >> >> Looking at the last release date: would it make sense to consider >> another 1.9.x maintenance release in the next couple of weeks? >> >> Regards >> >> ap > > -- > Andrew Gaul > http://gaul.org/
