About Feedback timeout

[Giorgos Keramidas]

On 2005-04-05 22:56, Matteo Riondato <rionda at gufi.org> wrote:
> While digging in the PR database to find some PRs I can help to solve,
> I found many PRs still open even if they are really old, refer to old
> and no longer supported -RELEASE or the submitter didn't reply to
> feedback request.
>
> I'm wondering what should be done with them and if I should point them
> out, replying to each one of them or if I can post a list of PRs that
> I think can be closed.

I have been running a weekly cron job on freefall for some years now,
that finds problem reports in "feedback" state and tracks down their
last time of modification.  The output is available online at:

        http://people.freebsd.org/~keramida/pr/feedback.txt

Some times, I use it to find problem reports that may be interesting but
seem to have been dropped for lack of time, or any other reason.  A good
way to handle these is to try to contact the original submitter and see
if they are still having problems, if they have tried a more recent
FreeBSD version (possibly solving the original problem), or if they no
longer care about this because they moved on to work on other things.

> The same apply for some "patched" PRs too.

Patched PRs are a bit different, because being in a "patched" state
means that they did get committed to HEAD.  They should be treated with
even more care, since getting them backported to non-CURRENT releases is
often just a matter of tracking down and notifying the committer who did
the original commit.