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"
> > To: proton@qpid.apache.org
> > Sent: Thursday, April 30, 2015 9:37:01 PM
+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"
> To: proton@qpid.apache.org
> Sent: Thursday, April 30, 2015 9:37:01 PM
>
+1
I'd like to see an official release with the SASL updates as soon as
practical.
-Ted
On 04/30/2015 09:37 PM, Rafael Schloming wrote:
I'd like to see one fairly soon. I'm currently working through a few
sasl-related interop issues between proton-c and proton-j, but once that is
done and g
On 05/01/2015 02:37 AM, Rafael Schloming wrote:
I'd like to see one fairly soon. I'm currently working through a few
sasl-related interop issues between proton-c and proton-j, but once that is
done and gordon's map fix lands, I think we would be in decent shape to put
out a 0.10 in short order.
I'd like to see one fairly soon. I'm currently working through a few
sasl-related interop issues between proton-c and proton-j, but once that is
done and gordon's map fix lands, I think we would be in decent shape to put
out a 0.10 in short order.
--Rafael
On Thu, Apr 30, 2015 at 3:06 PM, Rajith
I'm interested in knowing the timelines the community has in mind for the
0.10 release.
A tentative date for alpha and beta cycles would be helpful in planning the
work tasks and vacation time.
Regards,
Rajith
