Hi! Everything is in place to release 1.9.1, but I'd like to propose a different approach this time. Usually we run the live tests against each RC, but that means cutting new RCs to fix the important live tests that fail, which is not an optimal procedure.
I'd like to propose a "pre-release" period (a week?) to run the live tests and fix them so we can have a smooth and great 1.9,1 release. It would be great if we could coordinate some provider testing, as not everyone knows the details of every provider (and not everyone has an account in each one). Thinking about the most active contributors, it would be ideal if we could split the work like: @nacx: aws-ec2, digitalocean and chef. @abayer: Could you help with aws-ec2? @danbroudy: google-compute-engine, google-cloud-storage. @andreaturli: softlayer, docker. @zack: rackspace-cloudservers, rackspace-cloudfiles. @devjcsrj: can you give some love to ProfitBricks? @ilgrosso: could you rune the live tests on Azure Compute? @ccustine: would you be able to run the HPCloud Compute live tests? @gaul: blobmaster! :) @all-mailing-list-subscribers: Any live test feedback on any provider is very welcome, and PRs are very welcome too! Please, don't misunderstand this as an assignment of tasks! I'm just thinking out loud about a way to coordinate work so we can test and fix as many broken windows as we can, without duplicating efforts and without converting it in a tedious task. Running and fixing live tests (there shouldn't be many live tests failing) shouldn't be a tough effort, and the benefits for the project are huge. If there is an agreement, I'd propose a week of live test run&fix and cut the 1.9.1 release on July 15-20. Does this sound like a good plan? I.
