There are currently 9 issues targeting 1.6.3 [1] that are still open. Some of them have been started, others still have no progress. I'd like to include JCLOUDS-330 [2], but it can be workaround, so there should be no problem if it is delayed until 1.7.0.
What do we do with the rest of the issues? Can we delay the ones that have no progress until 1.7.0? It would be nice to have feedback from the reporters! Ignasi [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%20%221.6.3%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC [2] https://issues.apache.org/jira/browse/JCLOUDS-330 On 11 October 2013 05:08, Adrian Cole <[email protected]> wrote: > Thanks for leading this release, Andrew. > > -A > On Oct 10, 2013 12:01 PM, "Andrew Gaul" <[email protected]> wrote: > >> I plan to start the jclouds 1.6.3 release process late next week. If >> you would like to include a commit in this release, please ping the JIRA >> issue, GitHub pull request, or reply to this thread. I will also review >> and evaluate the following pull requests for backporting: >> >> https://github.com/jclouds/jclouds/pull/104 >> https://github.com/jclouds/jclouds/pull/164 >> https://github.com/jclouds/jclouds/pull/173 >> >> In terms of content, 1.6.3 should only include low-risk fixes and small >> features for existing users of 1.6. Higher-risk and breaking changes >> should only go into master which will become 1.7. In terms of pacing, >> we plan to start the release process for 1.7 shortly after 1.6.3 and >> will have some release candidate process similar to previous major >> releases. >> >> -- >> Andrew Gaul >> http://gaul.org/ >>
