On Tue, 2016-07-05 at 12:25 +0100, Robbie Gemmell wrote:
> On 2 July 2016 at 03:20, Justin Ross <[email protected]> wrote:
> > 
> > Hi, folks.  Here is an RC for 0.13.1.  Please test and place your
> > vote.
> > 
> > Source distribution:
> > 
> >   https://dist.apache.org/repos/dist/dev/qpid/proton/0.13.1-rc/
> > 

+1 (see NOTE below)

Checks:
- download, checksums 
- make all docs, ctest, install
- built & ran dispatch tests.
- ran Go examples by hand from installed gocode library
- quick check of installed C++ and Go documentation

NOTE: gpg gave me this:

gpg --verify  qpid-proton-0.13.1.tar.gz.asc qpid-proton-0.13.1.tar.gz
gpg: Signature made Fri 01 Jul 2016 10:08:26 PM EDT using RSA key ID C6B459DB
gpg: Good signature from "Justin Ross (CODE SIGNING KEY) <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: F1B5 7706 904F AD58 4D55  21D5 648A 8E57 C6B4 59DB

I don't usually do the .asc check so I don't know if this is normal.

> > Maven staging repo:
> > 
> >   https://repository.apache.org/content/repositories/orgapacheqpid-
> > 1082
> > 
> > Changes since 0.13.0:
> > 
> > 
> > https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=log;h=r
> > efs/tags/0.13.1-rc
> > 
> > These are signed and ready for GA if approved by vote.  I'll close
> > the vote
> > on July 11th.
> > 
> > Thanks,
> > Justin
> +1
> 
> I checked the RC out as follows:
>  - Verified the sig and checksum files.
>  - Checked LICENCE+NOTICE files present.
>  - Ran the CMake build, tests, and install.
>  - Built the Qpid Dispatch 0.6.x branch against the earlier install.
>  - Ran the JMS client HelloWorld example against the earlier built
> 0.6.x Dispatch router and the 6.0.4 Java broker.
>  - Used the staging repo to run the Qpid JMS client master build and
> tests.
>  - Used the staging repo to run the ActiveMQ master build and AMQP
> tests.
>  - Ran the Maven build and tests.
> 
> Robbie
> 
> ---------------------------------------------------------------------
> 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