The are currently 11 unresolved JIRAs assigned a 0.10 fix-for:
http://s.apache.org/ytK

Of those, 4 are listed as blockers:

https://issues.apache.org/jira/browse/PROTON-905
Long-lived connections leak sessions and links

https://issues.apache.org/jira/browse/PROTON-923
[SASL] PN_TRANSPORT_ERROR event not raised

https://issues.apache.org/jira/browse/PROTON-943
Bump library (.so) major version for proton-c libraries

https://issues.apache.org/jira/browse/PROTON-950
SASL PLAIN over cleartext should be supported

It would be good if any others JIRAs could be updated to indicate they
are considered blockers so we know what is actually remaining, or to
move them to either the 0.11 or no fix version if they won't be
tackled in 0.10 (which should be most things now; please lets get it
out, I'm starting to wish I did 0.9.2 so I can release the JMS client
:P )

Robbie

On 7 July 2015 at 13:26, Ken Giusti <kgiu...@redhat.com> wrote:
> Yay Rafi!  Thanks!
>
>
> A simple query of currently outstanding blocker JIRAs affecting 0.9+ shows 
> only three:
>
> https://issues.apache.org/jira/browse/PROTON-826  (unassigned)
> https://issues.apache.org/jira/browse/PROTON-923  (asticher)
> https://issues.apache.org/jira/browse/PROTON-934  (rschloming)
>
>
> The remaining open bugs affecting 0.9+ are:
>
> https://issues.apache.org/jira/browse/PROTON-826?jql=project%20%3D%20PROTON%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29%20AND%20affectedVersion%20in%20%280.9%2C%200.9.1%2C%200.10%29%20ORDER%20BY%20priority%20DESC
>
>
>
>
> ----- Original Message -----
>> From: "Rafael Schloming" <r...@alum.mit.edu>
>> To: proton@qpid.apache.org
>> Sent: Tuesday, July 7, 2015 1:28:17 AM
>> Subject: 0.10 alpha1
>>
>> As promised, here is the first alpha for 0.10. It's posted in the usual
>> places:
>>
>> Source code is here:
>>
>>     http://people.apache.org/~rhs/qpid-proton-0.10-alpha1/
>>
>> Java binaries are here:
>>
>>     https://repository.apache.org/content/repositories/orgapacheqpid-1036
>>
>> Please check it out and follow up with any issues.
>>
>> --Rafael
>>
>
> --
> -K

Reply via email to