+1

Built from source and ran 0-9-1 and 1-0 tests
started up the broker and kicked the tyres of the web ui

-- Rob

On Sun, 12 Jan 2020 at 23:14, Keith W <[email protected]> wrote:

> +1.
>
> My testing was:
>
> 1) Verified the sha512 checksums on all distribution artefacts
> 2) Verified signatures on all the distribution artefacts
> 3) Reviewed NOTICE/LICENSE files.
> 4) Ran apache RAT
> 5) Built from source bundle and ran test profiles: mms with AMQP1.0
> 6) Spun up a Broker from the binary distribution
>
>
> On Fri, 10 Jan 2020 at 15:16, Oleksandr Rudyy <[email protected]> wrote:
> >
> > +1
> >
> > * verified signatures and checksums
> > * built and ran tests from source bundle
> > * ran "hello world" example
> > * used web management console to create and bind queues
> >
> >
> > On Thu, 9 Jan 2020 at 17:00, Alex Rudyy <[email protected]> wrote:
> >
> > > Hi all,
> > >
> > > I built release artefacts for Qpid Broker-J version 7.1.7 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/7.1.7-rc1/
> > >
> > > The maven artifacts are also staged at:
> > > https://repository.apache.org/content/repositories/orgapacheqpid-1189
> > >
> > > 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=12346660
> > >
> > > 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-1189
> > > </url>
> > >     </repository>
> > > </repositories>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
>

Reply via email to