On Tue, May 23, 2017 at 6:42 PM, Nick Kew <[email protected]> wrote: > On Fri, 2017-05-19 at 14:22 -0500, William A Rowe Jr wrote: >> On Fri, May 19, 2017 at 2:21 PM, William A Rowe Jr <[email protected]> >> wrote: >> > [-0] Release current svn _timedlock API implementation in 1.6 >> >> My own vote, I suspect it has enjoyed 2/3 of the scrutiny needed >> to be called the "best available release" and should be ready to >> release soon, but not as soon as 1.6.1 tag is needed. > > I see you've done the deed. Thanks.
Getting there, apologies for the disruption of branches/1.6.x/ The changes to the unix internal accessors, which may still be perfectly useful, have made reverting the original commit especially problematic. I'm getting there but had to come up for air before testing a couple more reverts. Once that is done I'll ensure locks/unix/ is back in business (the threat/harm to other architectures is very limited.) This includes reviewing the backports for the os mutex _ex mode. > Do you want to follow up by rolling the RC? I can do it, but > I'm laid up with a 'lurgy, so it may be a day or two before I'm > fit for any such thing. Follow up testing should take a day or two in the first place, and it seems there was enthusiasm for one or two fairly straightforward fixes before this rolls out, so let's let 1.6.x branch settle for a day once this is complete (follow-up email to list once I can claim to be finished.) In the interim - for anyone disrupted you may wish to grab the apr/branches/1.7.x/ which preserves the whole _timedlock scheme for our next minor release. Hopefully won't slow anyone down from 1.x development.
