Should we publish 1.7 alpha/beta artifacts like we did pre-ASF? Ideally we would have done this regularly during the 1.7 development cycle.
If we can find a way to do this reasonably quickly (ideally, automatically!) I'm sure that would help. As it is (hope it's been smooth for you, Andrew G!), releasing so far has taken a bit too long, in my opinion, to consider this.
Should we mass-rename packages from org.jclouds to org.apache.jclouds? Doing this now might prove easier for users than deferring the migration.
I think there was already a thread discussing this somewhere. I'd personally prefer a significant breaking change such as this to be a 2.0 thing. But if we feel that will still be a while off, or if we need to do that sooner from an ASF perspective, then it's a bullet we'll just have to bite.
I liked Adrian's suggestion of trying to find a way to avoid a migration effort for users that is both a big rename *and* some significant functionality changes/deprecation, as we're going to be doing for 1.7 and 1.8 with de-async etc.
Should we should bring jclouds-chef into the main repository to simplify our repositories? This currently adds an extra step while releasing.
Would work for me - they've been stable for ages, see active use and improvements and don't feel significantly less generic that e.g. route53.
ap
