Hi, If Python 3.4 was the current version when a bug was reported, I would expect the version field of the bug set to Python 3.4. Maybe the bug has been fixed in the meanwhile, maybe not. Closing all bugs affected to 3.4 is a risk of loosing useful information on real bugs: closed bugs are ignored by default in "Search" operation.
Changing the version field: well, I don't think that it's useful. I usually ignore this field. And it would send like 3000 emails... I don't see the point. It's not uncommon that I fix bugs which 5 years old if not longer. Sometimes, I decide to look at all bugs of a specific module. And most of old bugs are still relevant nowadays. Sometimes, closing the bug as WONTFIX is the right answer, but it can only be done on a case by case basis. Note: Same rationale for Python 3.5, Python 2.6, or another other old Python version ;-) Bug triage is hard and requires plenty of time :-) Victor Le mer. 20 févr. 2019 à 16:05, Stephane Wirtel <steph...@wirtel.be> a écrit : > > Hi, > > As you know, Python 3.4 and 3.5 are in security mode and the EOL for > these versions are respectively 2019-03-16 and 2020-09-13. > > Number of issues > > 3.4: 1530 issues > 3.5: 1901 issues > > But some issues are not related to the security. > > Could we update these issues (non-security) to 3.6/3.7 & 3.8? > > Cheers, > > Stéphane > > -- > Stéphane Wirtel - https://wirtel.be - @matrixise > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/vstinner%40redhat.com -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
