+1
I just learned to ignore the ancient PRs; they were not adding much value.
If a PR looks like it could be resurrected, we might consider 1) assigning a
committer to help push it over the line, and 2) check back with submitter to
see if they can update it.
We tried the above a few times over the last couple of years and were able to
finish a couple of otherwise-stale PRs.
Thanks,
- Paul
On Thursday, May 31, 2018, 2:35:25 PM PDT, Timothy Farkas
<[email protected]> wrote:
Hi All,
There are a lot of open PRs. I think it would be good to close some of them in
order to identify the remaining PRs that require action to be taken.
Specifically I was thinking of first closing obsolete PRs and then see how far
that takes us. A PR could be considered obsolete if it is:
* Changing code or documentation that no longer exists.
* Adding documentation that is no longer correct.
* Has a note already on the PR that it needs to be closed because another PR
was opened.
Any thoughts?
Thanks,
Tim
