+1 My testing:
1) Verify md5/sha checksums on tar.gz source and binarys 2) run test profile dby.0-9-1 3) shared durable subscriptions with the JMS client over TLS 4) start embedded broker using the staging repo and publish and receive msg (using JMS client) 5) some tyre kicking in the Web Management Console Kind regards, Lorenz On Thu, 2017-11-09 at 08:03 +0000, Keith W wrote: > +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) Ran test profiles mms-1.0, bdb-1.0, bdb-0-10, bdb-0-10 (client > dependencies: Qpid JMS Client 0.27.0/0.26.0 / Qpid JMS AMQP 0-x 6.1.4) > 5) Upgraded a 6.1.4 broker, with a BDB backed vh with queue containing > messages from AMQP 0-91, 0-10, 1.0 sources, into a 7.0.0 one. Messages > consumed cross protocols. > 6) Generally kicked the tyres within the Web Management Console > 7) Tested OAuth2 integration against Google > 8) Published and received AMQP 1.0 messages using Rhea 0.2.7 (rhea examples) > 9) Published messages using the REST API > > On 8 November 2017 at 21:06, Rob Godfrey <rob.j.godf...@gmail.com> wrote: > > > > +1 > > > > * built from source and ran tests > > * exercised management console to create vhosts, queues, exchanges, etc > > * tested shared durable subscription functionality > > > > On 8 November 2017 at 12:12, Oleksandr Rudyy <oru...@gmail.com> wrote: > > > > > > > > +1 > > > > > > * verified signatures and checksums > > > * built from source distribution and ran all tests > > > * started broker, created new queue and exchange using web management > > > console, bound new queue to new exchange > > > * successfully ran hello world example using legacy JMS client with > > > AMQP 0-9 and 0-10 > > > * successfully ran hello world example using new JMS client for AMQP 1.0 > > > > > > On 8 November 2017 at 17:35, Oleksandr Rudyy <oru...@gmail.com> wrote: > > > > > > > > HI all, > > > > > > > > Apache Qpid Broker-J 7.0.0 RC3 is built and ready for testing. > > > > The following issues have been resolved since RC2: > > > > > > > > * QPID-8020 - [Broker-J] Rename binary and source distribution bundles > > > for > > > > > > > > broker-j > > > > * QPID-8023 - [Broker-J] Remove com.google.code.findbugs:jsr305 > > > dependency > > > > > > > > * QPID-8024 - [Broker-J] Reflect missing components and changes in > > > copyright > > > > > > > > dates in the NOTICE file > > > > > > > > The full list of new features, defect fixes and improvements can be > > > found in > > > > > > > > Jira: > > > > https://issues.apache.org/jira/issues/?jql=project%20% > > > 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-broker-7.0.0 > > > > > > > > > > > > The source and binary archives can be grabbed from here: > > > > https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.0-rc3 > > > > > > > > The maven artifacts are also staged for now at: > > > > https://repository.apache.org/content/repositories/orgapacheqpid-1121 > > > > > > > > Please test and cast your vote accordingly. > > > > > > > > Kind regards > > > > > > > > P.S. If you want to test it out using maven, you can temporarily add > > > this to > > > > > > > > your poms to access > > > > the staging repo: > > > > > > > > <repositories> > > > > <repository> > > > > <id>staging</id> > > > > > > > > <url>https://repository.apache.org/content/repositories/orgapacheqpid- > > > 1121</url> > > > > > > > > </repository> > > > > </repositories> > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
