I am conflicted... I'm still now sure what the real expected use-cases are, and don't feel that it's quite solid/stable enough for inclusion. But on the other hand, knowing the delays we have between API-changing releases, NOT having it in 1.6 basically puts it to bed for a long, long time, in case there *are* viable use cases for it.
I vote -0.9 (but am OK either way) > On May 19, 2017, at 3:21 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote: > > [ ] Release current svn _timedlock API implementation in 1.6 > > This seems to be the only questionable item remaining, and > this vote (and an enhancement may be vetoed, AIUI) is very > distinct from the poll on experimental features. > > Please vote, thanks.
