[pytest-dev] Hacktoberfest - Beginner Issues

[Brianna Laugher]

Some projects have a bug triaging guide, eg
http://docs.hood.ie/en/latest/developers/TRIAGING.html . Writing up the
existing process (eg intention of existing labels) may help more people
carry out bug triage.

On Sun, 9 Sep 2018 at 16:43, Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> I have seen a lot of projects use something like
> https://github.com/apps/stale to auto-close issues after a certain amount
> of time has passed without activity.
>
> On Fri, 7 Sep 2018 at 04:21, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
>>
>> On Thu, Sep 6, 2018 at 2:26 PM Maik Figura <maiksensi at gmail.com> wrote:
>>
>>> Hey everyone,
>>>
>>> I noticed that the issue tracker almost hit 500 issues. Would it be good
>>> to discuss how to handle issues in general (follow ups, etc) and on how
>>> to maybe reduce the amount of outdated issues (I am not even sure there
>>> are outdated ones...). Do we maybe have examples how other projects do
>>> this? Or maybe this was already discussed and I just missed it?
>>>
>>>
>> Hi Maik,
>>
>> (I'm adressing the contents of the email, not the title :))
>>
>> The number of open issues is something that bugs me. One of the reasons
>> that labels like "question" and "needs information" were created was that
>> we could periodically go over issues marked with them and close if they
>> have been inactive after some time, but this is something that has to be
>> done regularly.
>>
>> I would love to know how other projects which also face a large number of
>> issues deal with this.
>>
>> Cheers,
>> Bruno.
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20180909/c45ebd5e/attachment.html>