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/
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
