#18 Update the FTBFS policy
Merged 2 months ago by churchyard. Opened 2 months ago by churchyard.
fesco/ churchyard/fesco-docs ftbfs  into  master

@@ -35,36 +35,42 @@ 

  .  Maintainers should either fix and close the bug or acknowledge that

      they are working on a solution by setting the state to ASSIGNED.

  .  If an FTBFS or FTI bug remains in the NEW state for at least *1

-     week*, any concerned party can set a *NEEDINFO* for the maintainer to

-     respond and send an *e-mail reminder* with the Bugzilla link to

-     `<component_name>-\maintainers@fedoraproject.org`, cc'ing the

-     link:https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org/[devel

-     mailing list] (so there is a public record) and commenting on the bug

-     about doing so.

+     week*, any concerned party can set a *NEEDINFO* asking the maintainer to

+     respond.

  .  If the bug remains in NEW state for at least another 3 weeks after

-     the NEEDINFO and e-mail (= at least for *4 weeks* in total), any concerned party

-     can send *another comment and e-mail* (as in the previous point).

+     the NEEDINFO (= at least for *4 weeks* in total), any concerned party

+     can send *another comment* asking the maintainer to respond.

  .  If the bug remains in NEW state for at least another 4 weeks after

-     the second e-mail and comment (= at least *8 weeks* in total), the package

-     will be *orphaned*. Orphaning can be requested via a releng issue.

+     the second comment (= at least *8 weeks* in total), the package

+     *will be orphaned*. Orphaning can be requested via a releng issue.

  .  The normal

      link:https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers[Orphaned

      package that needs new maintainers procedure] will be followed for the

      packages orphaned in this way, leading to their *retirement* if nobody

      adopts them.

- .  A week before the *mass branching*, any packages which still have

-     open FTBFS bugs from the previous release will be *retired*. This can be

-     requested via a releng issue.

+ .  Cca six weeks before the Fedora N *mass branching*, packages that weren't

+     successfully rebuilt at least in Fedora N-2 are collected and weekly reminders

+     are sent to affected maintainers and the Fedora devel mailing list.

+ .  Cca a week before the Fedora N *mass branching*, packages that weren't

+     successfully rebuilt at least in Fedora N-2 will be *retired* assuming

+     there have been at least 5 warnings on the devel mailing list.

+     The bug status has no effect on this retirement.

+     This can be requested via a releng issue.

  .  A week before the scheduled *beta freeze*, any packages which have

-     open FTI bugs in the NEW state with at least 8 weekly reminders will

-     be** retired** from the relevant release and rawhide (in addition to

-     being orphaned). (Releng ticket for this needs to be opened at least a

-     week before the freeze, but can be opened sooner.)

+     open FTI bugs in the NEW state for at least 8 weeks with at least 2

+     reminder comments *will be retired* from the relevant release and rawhide

+     (in addition to being orphaned). (Releng ticket for this needs to be opened

+     at least a week before the freeze, but can be opened sooner.)

  .  The previous point repeats for the *final freeze*.

  

- (Effectively, packages will be retired after 14 weeks or sooner if there

- is no maintainer response and the package is orphaned, or after 6½

- months if the maintainer responds to FTBFS but the bug is not fixed.)

+ Example FTBFS retirement:: Soon before Fedora 31 branches, packages that were

+ last successfully rebuilt on Fedora 28 (or even sooner) will be retired.

+ In the time of Fedora 31 GA, all packages were rebuilt on a currently supported

+ Fedora (at least Fedora 29).

+ 

+ (Effectively, packages that fail to build will be retired after 14 weeks or

+ sooner if there is no maintainer response and the package is orphaned,

+ or after 13 months if the maintainer responds but the package is not fixed.)

  

  When releng performs the

  link:https://docs.pagure.org/releng/sop_mass_rebuild.html[mass rebuild],

rebased onto a87b710

2 months ago

rebased onto c80536f

2 months ago

Pull-Request has been merged by churchyard

2 months ago