Hi Thomas, Thanks for bringing this up! Hardcoding the date for 4.6 EOL is something we should discuss.
So far we have had a few releases since the beginning of the year: January, May and June, with contributions from the community. Given our overhead is relatively small (review merge a PR and make the release), and if a user is going through the trouble of contributing a fix it probably means it blocks/bother them enough to care to make a PR, I personally don't mind extending our commitment of making new 4.6 releases contributions until the end of the year, and stating that officially. I would like to hear what others think about this though. Cheers, On Wed, Jul 1, 2020 at 7:49 AM Thomas Grainger <tagr...@gmail.com> wrote: > By most calculations mid-2020 has now passed, > > I propose hardcoding mid-2020 to some date in the (very) near future, > eg 2020-08-01 > > Thomas Grainger > _______________________________________________ > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
