#2244 Update the FTBFS policy
Closed: Accepted a month ago by zbyszek. Opened a month ago by churchyard.

This is a proposal to update the FTBFS policy based on the feedback received after the F30FTBFS retirements and https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NKFYAWL4GWYR37C6XA63JMNBZYEM6BI3/

Full changes: https://pagure.io/fesco/fesco-docs/pull-request/18

Practical changes with rationales:

  • less weekly bugzilla spam required
    • maintainers tend to redirect too much traffic to /dev/null
  • no need for public shaming on the devel list
    • the need to do this prevented most of the orphaning - orphaning is good, because there are procedures in place to alert all interested parties,
    • this could have created unfriendly environment, some maintainers consider such e-mail as personal attacks
  • orphaning of the packages can happen automatically
    • because there is no need of human intervention
    • I will make sure we actually do this
  • retirement only happens if there were reminders, not out of the blue
    • the "out of the blue" retirement was the most criticized part of the F30FTBFS retirements
  • maintainers can sweep FTBFS under the rug, but only for a specified time
    • this is a compromise between "this needs to be fixed or we'll retire it" and "maintainers are intimidated by this militant policy"
  • maintainers cannot avoid the retirement by closing the bugzillas as WONTFIX
    • this actually happens

APPROVED (+5,0,-0)

(counting myself as +1)

Metadata Update from @churchyard:
- Issue tagged with: pending announcement

a month ago

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata