Hi, folks. I know we still have work to do, and doing one release is only a milestone, not a destination. Nonetheless, we ought to set wheels in motion to cut a release so that folks using jclouds can get updates and also switch to the new repositories we now publish to.
Personally, I could use 1.6.1 in the near future, so am happy to assist, including testing. I'm already using snapshots and will be using them in production tomorrow. We probably need a release manager and a certain amount of mentor support so that we don't fall in holes such as those I recently noticed in the curator release. Who can volunteer to manage the release of jclouds 1.6.1? Which mentors can help us ensure this release will be acceptable from a process POV? Really excited that we've come so far, so fast. Thanks to the several who've put in many hours towards this. -A
