On Fri, 2019-08-09 at 13:07 -0500, Michael Cronenworth wrote: > On 8/9/19 8:50 AM, Miro Hrončok wrote: > > Because if we don't, people just gonna ignore FTBFS forever. > > > > Could we have known that gettext will be unretired right away anyway? Probably > > yes, but nobody got time / energy / resources to do any kind of analysis of the > > FTBFS packages. > > > > Next time, I hope that FTBFS bugs for critical component are actually actively > > solved sooner than the retirement happens. We can try to be more aggressive with > > the reminders, but I don't know if that helps, because even currently, packages > > just switch the Bugzilla to ASSIGNED to stop them. > > Instead of spending your time on better nag e-mails why don't you look at > contributing patches? Do you know he doesn't? But regardless, one person can run an FTBFS notification system. One person cannot fix all the FTBFS bugs. It's similar to the blocker bug process: a couple of us in QA can handle discovering, reporting and tracking blocker bugs. We can't *fix* them all (though I try to fix as many as I have time and ability to). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
