Re: Fixing Two Old PRs

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

On Wed, 23 Feb 2011 19:37:49 +0100
Dalibor Gudzic <dalibor.gudzic%gmail.com@localhost> wrote:

> Is there a time limit for old PRs upon which they sorta expire or
> something? I also got one that I submitted, but got no response for
> about a year or less. I understand devs don't have time to solve every
> PR, I'm just interested to know if PRs ever expire, or they get looked
> on after a while.

A PR will not magically expire, but if it's in the "feedback" state
(because a question or testing was requested and the submitter didn't
yet answer), then after a reasonable period it can be closed if no
other person experiences the same problem...

Certain rare bugs get assigned to the analyzed or suspended state,
where they also can linger a long while.  If a bug is too old and noone
complained about it for too long while the new code is known to have
been improved in that area, it may also occasionally be closed
(especially if it concerns a no-longer supported NetBSD version).
Another reason to close a PR is an invalid submitter email address,
because it prevents feedback.

When a new PR is submitted, or when a new follow-up post is sent for a
PR, the netbsd-bugs (or pkgsrc-bugs depending on its category) list
also receives a copy, and this is good to gain attention back on the
PR.  Of course, you can also CC another relevant mailing list when
posting a follow-up, too.

If a PR lacks necessary information or is ambigious, it is also likely
to get a quick read but to then be ignored a while, unless the issue is
of interest enough for someone, who'll request more information.  So
sending as many details as possible also helps.

Jeremy already mentioned how to append a follow-up to a PR; It's also
possible to verify your PR's state and full follow-up using
http://www.netbsd.org/support/query-pr.html

I hope this answers your questions,
-- 
Matt