+1 from me

Ran 0-9 and 0-10 tests.  Ad hoc testing of the management UI.

-- Rob

On 27 October 2016 at 18:17, Keith W <[email protected]> wrote:

> +1.
>
> My testing was:
>
> 1) Verified the md5/sha checksums on all distribution artefacts
> 2) Verified signatures on all all distribution artefacts
> 3) Built/ran test profiles mms for 0-9 and 0-10 from source bundle
> 4) Ran hello world against staged maven artefacts against broker from
> binary distribution artefact
> 5) Ran Joram tests using Qpid JMS Client 0.11.0 and the 0.11.1 against
> broker from binary distribution artefact.
>
> No issues encountered.
>
> On 24 October 2016 at 11:52, Oleksandr Rudyy <[email protected]> wrote:
> > Hi all,
> >
> > A release candidate for the next 6.0.5 release of the Qpid Java
> > Components has been created.
> >
> > A number of important defect fixes and improvements have been made in
> > this release.
> > The list of changes can be found in Jira:
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.5
> >
> > Please test and vote accordingly.
> >
> > The source and binary archives can be accessed here:
> > https://dist.apache.org/repos/dist/dev/qpid/java/6.0.5-rc1
> >
> > Those files and the other maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1090
> >
> > Kind regards
> > Alex
> >
> > P.S. For testing of 6.0.5 maven artifacts please add the staging repo as
> below:
> >
> >   <repositories>
> >     <repository>
> >       <id>staging</id>
> >       <url>https://repository.apache.org/content/
> repositories/orgapacheqpid-1090</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]
>
>

Reply via email to