On Thu, Nov 14, 2013 at 10:18:02AM -0800, Andrew Bayer wrote: > 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?
I prefer to release 1.7 sooner rather than later. Three thoughts for 1.7: 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. Should we mass-rename packages from org.jclouds to org.apache.jclouds? Doing this now might prove easier for users than deferring the migration. Should we should bring jclouds-chef into the main repository to simplify our repositories? This currently adds an extra step while releasing. -- Andrew Gaul http://gaul.org/
