Sounds good to me. I'd really like to have the issue (don't remember the id) to configure the versioning in the "sub-repos" completed for 1.7.
It has been done in several repos but not in all of them (at least jclouds-labs is still remaining), and I think it is important that we have a consistent configuration in all pom.xml. Initially Zack had the issue assigned (do you think you'll have some time to spend on it before releasing 1.7?) but I'll be happy to take it if needed. So with 1.6.3 aiming to be out next week, I'd like to put a target date on 1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan to do the first RC on Monday, December 9th. There are a fair number of issues still open against 1.7.0 - see https://issues.apache.org/jira/browse/JCLOUDS-299?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%20%221.7.0%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC But I've created new 1.7.1 and 1.8.0 versions in JIRA (and 1.6.4, for that matter), so we can move issues to those releases if appropriate (I just did for a few, will go through the remaining issues in more detail later today/tomorrow). It looks like the ones most likely not to get done for 1.7.0 are the remaining de-async related ones, and I'm fine with pushing that off to 1.8.0. Thoughts? A.
