RetroSearch Browse

Wed Feb 20 11:02:53 EST 2019 · https://mail.python.org/pipermail/python-dev/2019-February/156402.html

Hi Steve,

I reply on the mailing list

On 02/20, Steve Dower wrote:
>It'll make same noise, sure, but if we schedule a bulk close of issues
>that have not been touched since 3.6 was released then at least it'll be
>easy to "mark all as read". And searching for current issues will become
>easier.
As Serhyi proposed, a one by one could be interesting, to be sure we
"migrate" the right issue to the right version.
>
>I'm always in favor of cleaning up inactionable bugs (as much as I'm in
>favor of keeping actionable-but-low-priority bugs open, which causes
>quite a few conflicts at work...)
>
>That said, maybe it makes sense to wait until 2.7's EOL and do them all
>at once?
I have already started with some issues.

-- 
Stéphane Wirtel - https://wirtel.be - @matrixise

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2019-February/156402.html below:

[Python-Dev] Question - Bug Triage for 3.4 & 3.5