On Sat, Oct 19, 2019 at 2:11 PM Branko Čibej <br...@apache.org> wrote: > By the principle of least surprise, I think it > would be better to merge to trunk, create a > new 1.13.0 release candidate
+1 > and (maybe?) restart the soak. I support this idea even if the soak must restart or be extended. Rationale: * we still get 1.13 out in time for the holidays * we get one STS release with Py3 before the next LTS release * we support Py3 before Py2 goes "out of support" -- there's no "lapse in coverage" for customers who have IT policies about that (One corporate or government customer wrote to users@ some months ago and specifically mentioned concern because of such a policy; I'd love to reply and say that Py3 is supported on time.) Bottom line: we'll be a little late in the release but in exchange we'll have one really whiz-bang compelling new feature -- that people have been asking for -- to write about in the release notes. Nathan
