[Python-Dev] "Good first issues" on the bug tracker

Lysandros Nikolaou lisandrosnik at gmail.com
Thu Feb 21 16:26:49 EST 2019

On Thu, Feb 21, 2019 at 9:59 PM Cheryl Sabella <chekat2 at gmail.com> wrote:

> I agree completely. We normally add the "Easy" or "Easy (C)" keywords to
>> mark these (the latter for issues that involve C code), and these are
>> collected under the "Easy issues" link at the left hand side of the
>> tracker.
>> Any reason to change from this process?
Yeah, I think some kind of separation between the two would be needed in
this case. There are some of us newbies, who frequently click the "Easy"
button, so that we find some issue to tackle. Some kind of marking an issue
as a "sprint issue" would quickly tell me that the issue is not available
to take on.

If that's not done, there's the risk that a good number of easy issues
would be closed until the sprint.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190221/2320dedb/attachment.html>

More information about the Python-Dev mailing list