Is including jclouds 2.0 too big of a change to consider, what do people think? If that's considered too risky then I suggest following with a 0.11.0 not too long after, including jclouds 2.0. There's already work to get it running with Brooklyn at https://github.com/apache/brooklyn-server/pull/415 <https://github.com/apache/brooklyn-server/pull/415> and https://github.com/apache/brooklyn-server/pull/409 <https://github.com/apache/brooklyn-server/pull/409>.
Svet. > On 16.11.2016 г., at 13:22, Aled Sage <aled.s...@gmail.com> wrote: > > Hi all, > > It's far past time that we did a Brooklyn 0.10.0 release! I suggest we aim > for that soon. > > To that end, I suggest the following steps: > > * Deal with open PRs: > o People shout out about any PRs you think are very important to > be merged, before that release. > o Review open PRs > (for any that won't get merged into 0.10.0, clearly mark them as > such and say why). > * Any pending/remaining work: > o Give people until Friday evening (uk time) to submit any other > very important PRs that are being working on. > o People shout out about any known issues that they see as > blockers for a release. > * Do some initial testing, using master (before Friday). > * Aim to produce a first release candidate on Friday evening (uk time). > * Do the usual QA/fix cycle until the release is ready. > * Write release notes, etc. > > Of the first steps, reviewing the PRs is a big piece of work! If you have > time to help, then please lend a hand by reviewing and/or testing the PRs, > and commenting on them. > > I don't think we should try to squeeze lots of additional PRs into 0.10.0 - > there is already a huge amount in there compared to 0.9.0! > > Richard, are our release process docs up-to-date at [1]? > > Aled > > [1] > http://brooklyn.apache.org/developers/committers/release-process/index.html > >
