On 28 September 2016 at 12:24, Andreas Mueller <t3k...@gmail.com> wrote: > > > On 09/28/2016 02:21 PM, Nelle Varoquaux wrote: >> >> >> I think the only ones worth having are the ones that can be dealt with >> automatically and the ones that will not be used frequently: >> >> - stalled after 30 days of inactivity [can be done automatically] >> - in dispute [I don't expect it to be used often]. > > I think "in dispute" is actually one of the most common statuses among PRs. > Or maybe I have a skewed picture of things. > Many PRs stalled because it is not clear whether the proposed solution is a > good one.
On the stalled one, sure, but there are a lot of PRs being merged fairly quickly. So over all, I think it is quite rare. No? > It would be great to have some way to get through the backlog of 400 PRs and > I think tagging them might be useful. > We rarely reject PRs, we could also revisit that policy. > > For the backlog, it's pretty unclear to me how many are waiting for reviews, > how many are waiting for changes, > and how many are disputed. > Tagging these might help people who want to review to find things to review, > and people who want to code to pick > up stalled PRs. That sounds like a great use of labels, thought all of these need to be tagged manually. > _______________________________________________ > scikit-learn mailing list > scikit-learn@python.org > https://mail.python.org/mailman/listinfo/scikit-learn _______________________________________________ scikit-learn mailing list scikit-learn@python.org https://mail.python.org/mailman/listinfo/scikit-learn
