On 18 April 2018 at 21:01, Robbie Gemmell <[email protected]> wrote: > Hi folks, > > I have put together a second spin for a Qpid Proton-J 0.27.0 release, please > test it and vote accordingly. > > The source and binary archives can be grabbed from: > https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.0-rc2/ > > The maven artifacts are staged for now at: > https://repository.apache.org/content/repositories/orgapacheqpid-1137 > > The JIRAs assigned are: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12342819 > > Regards, > Robbie > > P.S. If you want to test things out using maven with your own build > 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-1137</url> > </repository> > </repositories> > > The dependency for proton-j would then be: > > <dependency> > <groupId>org.apache.qpid</groupId> > <artifactId>proton-j</artifactId> > <version>0.27.0</version> > </dependency>
+1 I checked things over as follows: - Verified the signature and checksum files. - Checked for LICENCE and NOTICE files in the archives. - Verified the source archive licence headers with mvn apache-rat:check. - Ran the build and tests from source archive. - Used the staged bits with a Qpid JMS master build and ran the tests. - Used built client in the Qpid Broker-J master build and [sys]tests. - Used the client and Qpid Broker-J master to run the joram tests. - Ran some manual tests with PN_TRACE_FRM enabled to verify RC1 issue fixed. - Used the staging repo and built client with the ActiveMQ Artemis master build and AMQP tests. - Ran the JMS HelloWorld example against Broker-J, Dispatch, and Artemis masters. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
