Johan Corveleyn wrote on Wed, 22 Apr 2020 12:15 +00:00:
> In fact, there is very little pressure on getting this in 1.14.0 GA,
> because (1) it only affects testsuite-runners on Windows, of which
> there are extremely few :-), and (2) the workaround is simple (just
> use Py 2.7 for running the testsuite on Windows). Not worth taking
> risks for IMHO.
>
> The only actual "damage" is perhaps marketing. Now we can't claim
> "Full Py3 support" in big letters, we need to add a footnote pointing
> to a known issues section in the release notes or something ...
Fair point. I guess the issue could at least be mitigated by adding the
relevant revisions to STATUS and pre-approving them (by casting
"+1 (for 1.14.1, or 1.14.0 if the soak is restarted)" votes) ahead of
the .0 release, so as to enable the small print to at least be
definitive.
Cheers,
Daniel
Received on 2020-04-22 14:54:19 CEST