+1. My testing was:
1) Verified the md5/sha checksums on all distribution artefacts 2) Verified signatures on all the distribution artefacts 3) Ran apache RAT 4) Built/ran test profile mms/bdb 0-9/1.0 from source bundle (Qpid JMS Client 0.26.0/0.29.0) 5) Generally kicked the tyres within the Web Management Console using Broker from the tar,gz bundle 6) Spun up an embedded Broker-J using the staged maven artefacts. On 27 February 2018 at 14:57, Oleksandr Rudyy <[email protected]> wrote: > Hi all, > > I built a release candidate for a Qpid Broker-J 7.0.2. > Please give it a test out and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.2-rc1 > > The maven artifacts are also staged for now at: > https://repository.apache.org/content/repositories/orgapacheqpid-1132 > > The JIRAs currently assigned are: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12342782 > > Regards, > Alex > > P.S. For testing of maven broker staging repo artifacts, please add into to > your poms the staging repo as below: > > <repositories> > <repository> > <id>staging</id> > <url> > https://repository.apache.org/content/repositories/orgapacheqpid-1132</url> > </repository> > </repositories> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
