----- Original Message -----
> From: "Cliff Jansen" <cliffjan...@gmail.com>
> To: "proton" <proton@qpid.apache.org>
> Sent: Thursday, September 18, 2014 12:04:25 PM
> Subject: Re: 0.8 release prep
> 
> I would like someone with better Python/SWIG expertise to take a look
> at PROTON-687, at least to confirm if the python swig wrapper for
> pn_delivery_set_context (and other similar "borrowed" references) are
> the culprits, or the victims of a bug elsewhere.
> 

I can repro this on linux, simply by running the python tests under valgrind.

I've updated the bug, will take a look.

-K


> I would like to update PROTON-581 (Schannel ssl for windows) for
> changes in the SSL internal api and get it checked in.
> 
> I would also like to take a closer look at PROTON-660 (openssl on
> Windows) or have someone else review it for rc1.
> 
> On Thu, Sep 18, 2014 at 8:32 AM, Clebert Suconic <csuco...@redhat.com> wrote:
> > I have a commit that I would like to send towards a contrib component:
> >
> > https://github.com/clebertsuconic/qpid-proton/commit/ab423a90f6b1e6d06c84615c5724497a3f9e8533
> >
> >
> >
> > The current code is always encoding it as Bytes, and I need the ProtonJ as
> > an output on the case of the JMS component.
> >
> >
> >
> > On Sep 18, 2014, at 11:15 AM, Miguel da Rocha Correia Lima
> > <mcorreial...@landix.com.br> wrote:
> >
> >> Hi Rafael,
> >>
> >>        The PROTON-661 was useful for us. We are working with this patch
> >>        without any error.
> >>        We supose that it can be useful for others.
> >>
> >> Miguel da Rocha Correia Lima
> >> miguel at landix dot com dot br
> >>
> >> Em 18/09/2014 11:55, Rafael Schloming escreveu:
> >>> Hi Everyone,
> >>>
> >>> I'd like to put out a 0.8 RC soon. I will be going through JIRA shortly
> >>> in
> >>> order to triage any remaining issues. If there are any particular issues
> >>> that you feel strongly should be included in 0.8, please follow up on
> >>> this
> >>> thread and bring them to my attention.
> >>>
> >>> --Rafael
> >>>
> >>
> >
> 

-- 
-K

Reply via email to