For reference, Andrew ultimately closed the PROTON-1645 go+libuv issue, indicating that after cleaning up his source tree he was later unable to reproduce it himself. There may be improvements that can be made there, but they are not show stoppers.
On 20 October 2017 at 15:42, Alan Conway <[email protected]> wrote: > I'll fix the libuv proactor stuff but I'm not convinced that's a show > stopper. I'd be inclined to include it in a respin if there is one when its > ready but not hold up the release. > > On Thu, Oct 19, 2017 at 10:31 PM, Andrew Stitcher <[email protected]> > wrote: > >> Some more problems found on FreeBSD and building with a libuv proactor >> on Linux: >> >> PROTON-1642, PROTON-1643, PROTON-1644, PROTON-1645 >> >> Everything I've found today is all either on uncommon platforms (RPi, >> FreeBSD) or using the less tested libuv proactor. >> >> So despite finding these, it's actually not clear to me whether they >> are really important enough to nix the release. >> >> What do others think? For the moment I think I'm going to abstain. >> >> Andrew >> >> On Wed, 2017-10-18 at 18:29 +0100, Robbie Gemmell wrote: >> > Hi folks, >> > >> > I have put together a first spin for a Qpid Proton 0.18.0 release, >> > please test it and vote accordingly. >> > >> > The source archive can be grabbed from: >> > https://dist.apache.org/repos/dist/dev/qpid/proton/0.18.0-rc1/ >> > >> > The JIRAs currently assigned are: >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231 >> > 3720&version=12338903 >> > >> > It is tagged as 0.18.0-rc1. >> > >> > Regards, >> > Robbie >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
