On 26/11/2020 18:16, Matti Picus wrote:
Now that the re fixes are in for py3.7, I think our primary branch for
development should be py3.7, with backports to py3.6 if needed. PEP 494
for python 3.6 has that version in a security-fixes-only stage, so we
should adopt a similar strategy (although some bug-fixes may be needed,
especially around utf8 problems that are still cropping up).
I think it's a bad idea to reverse the direction of merges now. We still
have quite a few fixes coming in for 3.6.
Toward that end, I have updated the buildbot configuration to build
nightlies off the py3.7 branch instead of the py3.6 branch. So if you
wish to obtain a newer build of py3.6, you will need to manually trigger
the buildbots.
+1 though ideally we would just run both as nightlies.
This does not change the status of the default branch.
Please let me know if this was too fast and you feel we should continue
to use py3.6 as our primary branch for development.
Matti
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev