Re: Non-responsive maintainer: mruprich (Michal Ruprich)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Good point, thanks!

On 22/04/2020 10:42, Miro Hrončok wrote:
On 22. 04. 20 10:21, Martin Sehnoutka wrote:
Regarding the abrt reports: I can see a lot of them are for Wireshark, but given the size of Wireshark codebase and speed of its development it would require a huge effort to fix all of them.

Not related to Michal at all, more general thought:

If the maintain is unable (for any reason including "no time") to solve the ABRT bugzillas, they should clearly state that and close them as CANTFIX, or at least unassigned themselves. Ignoring the report for a year is not good practice.

_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux