I was originally thinking a beta2 this week to help shake anything else out and hopefully enable an RC+ vote early next week.
PROTON-950 is a blocker and still open. Work has been done to restore support for PLAIN on non-SSL transport, but it seems some remains to actually use it in the other components. It'd also be good if Ted and Gordon could comment on whether what has been done meets the need from their perspectives based on earlier JIRA comments. I tried doing something yesterday with the reactive API bits that seem like it would be similar (modifying the settings of a new transport before use) to what would be needed to flip the new transport toggle, but couldnt actually see how to do it, hopefully someone more familiar with the python and C reactive bits can take a look at things. Robbie On 31 July 2015 at 14:18, Ken Giusti <kgiu...@redhat.com> wrote: > Arg! Sorry, PROTON-969 is a blocker! > > So, if that's not in by Monday... beta-2? > > -K > > ----- Original Message ----- >> From: "Ken Giusti" <kgiu...@redhat.com> >> To: proton@qpid.apache.org >> Sent: Friday, July 31, 2015 9:03:25 AM >> Subject: Re: 0.10 beta2? >> >> Hi Robbie - >> >> It doesn't look like there are any open blockers for 0.10. >> >> Can we branch 0.10 and put out release candidate 1? >> >> Here is the list of open JIRAs targetting 0.10: >> >> >> Bug PROTON-969 >> Cyrus SASL module calls sasl_server_init once for every incoming >> connection >> >> Bug PROTON-950 >> SASL PLAIN over cleartext should be supported >> >> Improvement PROTON-941 >> pn_transport_set_server should fail if invoked after binding. >> >> New Feature PROTON-855 >> Add axTLS (embedded SSL) support to proton-c >> >> New Feature PROTON-852 >> Implement pn_getaddrinfo,pn_getprotobyname for platforms that not support >> getaddrinfo(),getprotobyname() >> >> >> ----- Original Message ----- >> > From: "Robbie Gemmell" <robbie.gemm...@gmail.com> >> > To: proton@qpid.apache.org >> > Sent: Thursday, July 30, 2015 1:16:48 PM >> > Subject: 0.10 beta2? >> > >> > I think it would be good to do a second(/final) beta for 0.10 and keep >> > the process moving, hopefully then being able to spin an RC early next >> > week. >> > >> > One of the previous blockers has been reverted and bumped to 0.11 due >> > to various issues with the earlier change. The other has had some work >> > done for it and may or may not be complete, one good way to tell would >> > be to get folks to kick the tyres on it. >> > >> > There are currently 4 unresolved JIRAs assigned a 0.10 fix-for: >> > http://s.apache.org/ytK >> > >> > Robbie >> > >> >> -- >> -K >> > > -- > -K
