> The number of open issues is something that bugs me.
Dito. Because I think there are in fact issues that could be closed using
automated mechanisms.
> I would love to know how other projects which also face a large number of
issues deal with this.
I want to second Brianna's two topics:
> ... auto-close issues after a certain amount of time has passed without
activity.
To me that is a good mechanism, as long as it is automated and only happens
if we wait for feedback ("needs information" label for example can we
closed if we did not get a reply within X weeks).
This brings me to the second suggestion, which is a (bug) triaging guide.
> Writing up the existing process (eg intention of existing labels) may
help more people carry out bug triage
I think we would gain most by automating the process of closing tickets
where no follow up was given (from a users side). But this needs to be done
very carefully and in a documented way.
I am not sure there are more ways to help managing the immense amount of
issues (with the same amount of resources). Also, I dont think the bar to
submit a issue should be raised to ensure some sort of quality or else, but
instead it makes sense to automate the process of closing issues fast in a
documented and transparent way. Does pytest have some sort of process to
say "no" to requests (issue type doesnt really matter here if you ask me).
Is this even needed or do we already handle this in a good way?
One of my goals for the next Hackergarten Meetup in Stuttgart
(Hacktoberfestgarten in this case) will be to have a look at more projects
and see how they manage this and to come up with a proposal for pytest, so
we have something to discuss. If you have more input here, let me know so I
can work that in.
Best,
Maik.
On Sun, 9 Sep 2018 at 08:44, Brianna Laugher <brianna.laug...@gmail.com>
wrote:
> 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.laug...@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 <nicodde...@gmail.com> wrote:
>>
>>>
>>> On Thu, Sep 6, 2018 at 2:26 PM Maik Figura <maikse...@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@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/
>
_______________________________________________
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
