On Thu, Jan 26, 2023 at 11:07:34PM +0100, Miro Hrončok wrote: > > Unfortunately, as seen by the lenght of the packages listed in my emails, > thsi is not always the case. Yeah. ;( > Some packagers do set the bugzillas to ASSIGNED to get rid of the reminders > and then they forget to actually fix the FTBFS, cannot figure out how to fix > it, are blocked on externalities that never happen, etc. Yep. Can happen to us all. > Oh but they are different. FTBFS are not urgent and the policy is only set > to retire packages that FTBFS for more than 2 release cycles. > > For a package to be considered for retirement in February 23, it would have > to fail to build: > > - During the Fedora 36 mass rebuild in January 22. > - During the Fedora 37 mass rebuild in July 22. > - During the Fedora 38 mass rebuild in January 23. > > That is not urgent, that is "not being fixed". Right. > We can make this even longer, but I don't think it'll make a difference -- > eventually we will just get a list of packages that aren't beign fixed, but > for a longer time. Yeah, no... kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
