qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: [VOTE] Proton 0.9 RC 2
Date Mon, 16 Mar 2015 16:54:26 GMT
Dominic has posted a further change for PROTON-834 that fixes a corner
case not seen when making an earlier change in 0.9.

I think we should include it if doing an RC3 to pick up the change
Alan also made earlier.

Robbie

On 16 March 2015 at 12:20, Robbie Gemmell <robbie.gemmell@gmail.com> wrote:
> [ +1 ] Yes, release Proton 0.9-rc-2 as 0.9 final
>
> I tested out RC2 as follows:
> - Checked license/notice files present.
> - Verified sigs and checksums match.
> - Built everything using cmake and ran the tests.
> - Verified building/running the Qpid C++ broker against proton-c.
> - Built proton-j and ran the tests using maven.
> - Verified using proton-j in the build+tests for the new Qpid JMS client.
>
> Robbie
>
> On 16 March 2015 at 05:04, Rafael Schloming <rhs@alum.mit.edu> wrote:
>> Hi Everyone,
>>
>> I've posted 0.9 RC 2 in the usual places. The source artifacts are
>> available here:
>>
>>     https://people.apache.org/~rhs/qpid-proton-0.9-rc-2/
>>
>> Java binaries are available here:
>>
>>     https://repository.apache.org/content/repositories/orgapacheqpid-1029
>>
>> The changes from RC 1 are very minor, I've appended the commit log if
>> you're interested in the details. Please have a look and register your vote:
>>
>> [   ] Yes, release Proton 0.9-rc-2 as 0.9 final
>> [   ] No, because ...
>>
>> --Rafael
>>
>> ================================================================
>>
>> commit b6506126afbc51bab4c97bf847f2f07f2cc4e6e2
>> Author: Rafael Schloming <rhs@alum.mit.edu>
>> Date:   Mon Mar 16 17:42:56 2015 +1300
>>
>>     Release 0.9-rc-2
>>
>> commit 0fbe80e2f81a1e8a2df55f6221b987391d5dc336
>> Author: Bozo Dragojevic <bozzo@digiverse.si>
>> Date:   Fri Mar 13 14:01:35 2015 +0100
>>
>>     PROTON-838: proton-hawtdispatch cannot connect with SSL
>>
>>     Remove one of calls to transport.connecting() as this causes
>>     an assert with SslTransport
>>
>>     (cherry picked from commit f8ca35f3e007b99e0a5365e154e067840adcefb0)
>>
>> commit ea01c014fedd8dff134131f93b7d957aabac70ec
>> Author: Alan Conway <aconway@redhat.com>
>> Date:   Wed Mar 11 11:17:23 2015 -0400
>>
>>     PROTON-836: Missing import SSLUnavailable in reactor.py.
>>
>> commit 59efe4f6b2ea597332a2191665c498dbf44b8bd8
>> Author: Gordon Sim <gsim@redhat.com>
>> Date:   Mon Mar 9 14:37:35 2015 +0000
>>
>>     NO-JIRA: lack of ssl support should not prevent Container being used
>>
>> commit 27851bbbba6d979342178817734423b83b37840a
>> Author: Robert Gemmell <robbie@apache.org>
>> Date:   Mon Mar 9 19:36:06 2015 +0000
>>
>>     add missing NOTICE file
>>
>>     cherry-picked from 36e32d2309bb0a96e63e9874758de8906a22ec69
>>
>> commit 77403b3c091b2c6dfcc766d978130a34f765ee29
>> Author: Kenneth Giusti <kgiusti@apache.org>
>> Date:   Mon Mar 9 13:38:56 2015 -0400
>>
>>     NO-JIRA: fix documentation build
>>
>>     (cherry picked from commit bc2b630eb969710b04a861797567ab2dc368020a)

Mime
View raw message