[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Python-Dev] PEP 581: Using GitHub Issues for CPython

On Thu, Mar 7, 2019 at 12:35 PM Matthew Woodcraft <matthew at woodcraft.me.uk>

> One part of this PEP stands out to me:
> | We should not be moving all open issues to GitHub. Issues with little
> | or no activity should just be closed. Issues with no decision made for
> | years should just be closed.
> I strongly advise against closing bug reports just because they're old.
> I know that the Python developers value trying to be a welcoming
> community. To many people, having a bug report that they put some effort
> into closed for no reason other than the passage of time feels like a
> slap in the face which stings harder than, for example, intemperate
> words on a mailing list.
> This is even more true if there won't be an option to re-open the bug,
> which seems to be what the PEP is saying will be the case.
> If a bug has been around for a long time and hasn't been fixed, the most
> useful information for the bug tracker to contain is "this bug has been
> around for a long time and it hasn't been fixed". Leaving the bug open
> is the simplest way to achieve that.
> (I think the above only goes for issues which are actually reporting
> bugs. Wishlist items are a different matter.)
> -M-

Thanks. A similar argument had been made by several other core devs in
person during Language summit 2018 as well as during the drafting of PEP
581, that we shouldn't be closing issues blindly.

I hear you (all) and I see the point. I agree that we shouldn't just be
closing all issues. I will edit the PEP sometime later today (or later this

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190307/762e2e35/attachment.html>