Aled, I don't know ;(
I'd _really_ like to have another RC cut that pulls in some/more/all of the current commits on master, but am unsure if that's desirable or possible? For eaxmple, these would be good: 1. The commits needed for Clocker, listed in my previous mail 2. Adding dynamic JMX sensors [1] because it's talked about in my latest blog post [2] 3. Andrea's Couchbase fixes for Clocker [3] Andrew. [1] http://github.com/apache/incubator-brooklyn/pull/311 [2] http://blog.abstractvisitorpattern.co.uk/2014/11/custom-sensors-in-brooklyn.html [3] http://github.com/apache/incubator-brooklyn/pull/317 -- -- andrew kennedy ? distributed systems hacker : http://blog.abstractvisitorpattern.co.uk/ ; On 15 November 2014 21:30, Aled Sage <[email protected]> wrote: > Andrew, > > Thanks for testing. Can clarify if you view any of these as blockers for a > Brooklyn 0.7.0-M2 release? > I guess given you said "I still have to do further testing" then no blockers > so far, but you'll continue testing and report back? > > Aled > > > > On 15/11/2014 19:55, Andrew Kennedy wrote: >> >> Hi. >> >> I have made another Clocker release using this RC, which is tagged as >> v0.7.0-brooklyn-m2 and available here: >> >> - >> https://github.com/brooklyncentral/clocker/releases/tag/v0.7.0-brooklyn-m2 >> >> I had to make a new version of brooklyncentral/advanced-networking >> with the same version as Brooklyn, available here as a tagged >> pre-release: >> >> - >> https://github.com/brooklyncentral/advanced-networking/releases/tag/v0.7.0-M2-incubating >> >> I also hd to incorporate changes from commits c77f9ff, f6e3f8f and >> 0a1e065 from post-RC0 Brooklyn master, to get Clocker to build. >> >> - >> https://github.com/apache/incubator-brooklyn/commit/c77f9ff4b658732291e8f176f54851b0b9f58e88 >> - >> https://github.com/apache/incubator-brooklyn/commit/f6e3f8ff9d7c5551f89d65a8e8157b83da54761e >> - >> https://github.com/apache/incubator-brooklyn/commit/0a1e0651786106803c7ffc2ca340768a8c545e97 >> >> I tested the basic operation of the Clocker blueprints, which seem OK. >> There were errors rebinding to a persistenceDir created by a later >> 0.7.0-SNAPSHOT Brooklyn, but this is probably an unusual situation. I >> still have to do further testing. >> >> Andrew. >> >> On 13 Nov 2014 13:41, "Aled Sage" <[email protected]> wrote: >>> >>> This is to call for a vote for the source release of Apache Brooklyn >>> 0.7.0-M2-incubating. >>> >>> The source tarball, including signatures, digests, etc can be found at: >>> >>> https://dist.apache.org/repos/dist/dev/incubator/brooklyn/apache-brooklyn-0.7.0-M2-incubating-rc2 >>> >>> The Git commit ID is be9fedde5f4fd553f9e26e1c61a0f2d27ba34e39 >>> >>> https://git-wip-us.apache.org/repos/asf?p=incubator-brooklyn.git;a=commit;h=be9fedde5f4fd553f9e26e1c61a0f2d27ba34e39 >>> >>> Release artifacts are signed with the following key: >>> https://people.apache.org/keys/committer/aledsage.asc >>> >>> Checksums of apache-brooklyn-0.7.0-M2-incubating-rc0.tar.gz: >>> MD5: 3de27b170fe1f1ebc3505296c070ddaa >>> SHA1: fbe72a1e0f5b1ca5647552ba173d667ede2105f8 >>> SHA256: 401a6cc4283cf08956a2f2bda7307dd70f1a98d52a04b3b58af890981ee2271b >>> >>> KEYS file available here: >>> https://dist.apache.org/repos/dist/release/incubator/brooklyn/KEYS >>> >>> Please vote on releasing this package as Apache Brooklyn >>> 0.7.0-M2-incubating. >>> >>> The vote will be open for 72 hours. >>> [ ] +1 Release this package as Apache Brooklyn 0.7.0-M2-incubating >>> [ ] +0 no opinion >>> [ ] -1 Do not release this package because ... >>> >>> >>> Thanks, >>> Aled Sage > >
