+1

I performed the following tests:
* Executed a full set of tests of Web Management console functionality in
Firefox and Chrome browsers
* Ran destruction tests with JMS clients for AMQP 0-9, 0-10 and 1.0
* Verified signatures and checksums
* Successfully built and ran tests from source distribution
* Ran hello world examples using Qpid JMS Client for AMQP 0-x version 6.3.3
and Qpid JMS Client for AMQP 1.0 version 0.40.0

On Mon, 24 Dec 2018 at 21:05, Oleksandr Rudyy <[email protected]> wrote:

> Hi all,
>
> I built RC2 for Qpid Broker-J version 7.1.0.
> The RC2 coming with the following fixes of issues in REST API:
> QPID-6948: [Broker-J] Fix generation of json response for operations
> returning void
> <https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=4ba0211>
> QPID-6948: [Broker-J] Fix handling of requests for unsupported category
> <https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=eccf0fc>
> QPID-6948: [Broker-J] REST requests returning inherited context should be
> able to return the inherited context from SystemConfig in REST API for
> versions 6.1 and 7.0
> <https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=e7a0f0f>
>
> 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.1.0-rc2
>
> The maven artefacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1166
>
> The new versions comes with 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=12338931
>
> Kind Regards,
> Alex
>
> P.S. For testing of maven broker staging repo artefacts, please add into
> to your poms the staging repo as below:
>
> <repositories>
>     <repository>
>       <id>staging</id>
>       <url>
> https://repository.apache.org/content/repositories/orgapacheqpid-1166
> </url>
>     </repository>
> </repositories>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

Reply via email to