Cassidy James :ea: :gg: :fh:
@mattdm ha, I didn't know Fedora did this! It's not an uncommon pattern, but I think it could be tweaked to be just as useful to maintainers while being more welcoming to issue reporters.
A simple solution could be to label *untriaged* issues as stale (or better: “Needs Attention”) after some time of inactivity with a gentler comment about, “Sorry we haven't been able to triage this. If you know it’s still an issue in the latest release, feel free to comment to help us triage it.”
Brodie Robertson
@cassidy @mattdm I think filtering based on whether there has been sufficient information provided, along with sorting based on when the last comment on the thread was made would go a long way in mitigating the issue. Nothing really will solve it without having people constantly going through and triaging old issues.
Brodie Robertson
@Conan_Kudo @cassidy @mattdm I think that's a bit more reasonable given the gap between releases
Neal Gompa (ニール・ゴンパ) :fedora:
@BrodieOnLinux @cassidy @mattdm I think there's a difference between Fedora's stale bug closure and what people do on GitHub. We auto-close bugs in RHBZ that target Fedora releases that are EOL. We automatically comment on those bugs informing them of why and tell them how to reopen it.
That's a lot kinder than the GitHub stale bots which aggressively close them in 60/90 days and tell you nothing.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.