Hi Bruno, Thomas,
given that thanks to the release automation work Bruno and the others
did put in,
the effort for doing releases after community contributions is very
sustainable.
I believe its fair to leave it open for until there was about a full
year without a new contribution/release.
Should the automation eventually change an the cost for doing the
releases changes,
it seems fair to drop the offer at that point.
We should however put it into very clear writing that any
backporting/bugfixing is up to the python2+pytest using community,
pytest-core will not handle any of that on volunteer time.
-- Ronny
Am 04.07.20 um 15:01 schrieb Bruno Oliveira:
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
<mailto: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 <mailto: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
_______________________________________________
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
