+1 Launched our validation pipeline which includes: - basic sends and receives - basic routing and filtering - JDBC message and config stores - message recovery - HTTP management and statistics - TTL, max queue size and max message size - SSL and SASL
One remark regarding the list of JIRAs though, it does not include https://issues.apache.org/jira/browse/QPID-8469 even though this fix is in 8.0.2 Olivier -----Original Message----- From: Oleksandr Rudyy <[email protected]> Sent: dimanche 18 octobre 2020 23:51 To: [email protected] Subject: [VOTE] Release Qpid Broker-J 8.0.2 Hi folks, I built release artefacts for Qpid Broker-J version 8.0.2 RC1. Please, give them a test out and vote accordingly. The source and binary archives can be found at: https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.2-rc1/ The maven artifacts are also staged at: https://repository.apache.org/content/repositories/orgapacheqpid-1206 The new version brings a number of improvements and bug fixes. You can find the full list of JIRAs included into the release here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12348808 Kind Regards, Alex P.S. For testing of maven broker staging repo artefacts, please add into to your project pom the staging repo as below: <repositories> <repository> <id>staging</id> <url> https://repository.apache.org/content/repositories/orgapacheqpid-1206</url> </repository> </repositories> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ******************************* This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. Its content and any attachment hereto are strictly confidential and must not be disclosed to any unauthorized third party. If you are not the intended recipient, please delete this email and any attachment and notify us immediately. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
