3 ms·
>The key is that an issue is only stale if a maintainer has asked a question of the person who filed the issue and that person is not responding. That's the onl
by jsmith45 6y ago
>The key is that an issue is only stale if a maintainer has asked a question of the person who filed the issue and that person is not responding. That's the only condition.
The possible issue with that criteria in general is that it need not actually be the original poster who replies with the needed details. Another user with the same problem could supply the needed details as well.
A different user supplying the answer is especially common on widespread issues that the maintainers are having problems tracking down. For example, it might be that the problem only reproduces on a certain version of a specific distro, or only if certain kernel configuration options are used. Those sorts of issues can be hard for the maintainer to discover, but might be easier for impacted users to locate.
You may well have stuff in place to handle this, but thought it was worth pointing out for completeness sake.
- habosa 6y agoMy opinion keeps changing on this one. Sometimes a non-author user will come by and say "this is happening to me too and here's some helpful logs". But other times a non-author user will just drive by and say "+1 any solution?". The former should reset the stale timer, the latter should not. I think in the end this depends on the project. In the end you need humans to pay attention to ongoing conversations or you'll always get some cases wrong.