This was more of a core-mentorship question (tracker management) than a
pydev question (Python development). But since we are here...
On 6/10/2019 11:41 PM, Mariatta wrote:
Hmm, I personally would still consider the additional issues as
duplicates. So I would make note in each of the duplicate issue saying
"this is caused by the same problem as bpo-X", and close them, and
attach the PR only to one bpo ticket.
To decide which one I would keep open, perhaps the oldest one, but maybe
it depends. Perhaps whichever that seems to contain most detailed info?
Maybe other core devs have other preferences?
No me. The general rule/convention has been to keep the oldest open and
close others. I put a note on the one kept open as to others closed.
If it is discovered after the fact that a patch for A fixed B, B can be
closed as 'out-of-date' with a comment 'fixed by ...'
--
Terry Jan Reedy
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/XKPMAEDXKUSOK6VPQXYRAP6JY4JYL37W/
