+1
I'd like to see the Python3 changes land on master soon after we cut a release
of SASL. Give py3 some time to shake out the bugs.
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To: proton@qpid.apache.org
Sent: Thursday, April 30, 2015 9:37:01 PM
Subject: Re: 0.10
Rafael H. Schloming created PROTON-877:
--
Summary: proton-c sasl client hangs on server pipeline
Key: PROTON-877
URL: https://issues.apache.org/jira/browse/PROTON-877
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526709#comment-14526709
]
Andrew Stitcher commented on PROTON-877:
[~rhs] could you give some more context
It appears the consensus is to have a release fairly soon.
I want be able to get the codec work in time for the 0.10 release.
These changes do have an impact on Robbies test code as some impl classes
are used directly.
Given the magnitude of the changes and the impact it has on the code base
and
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-877:
---
Attachment: tests.patch
Here are some tests illustrating various issues with this