Changes (Contigency) SoP

This document describes the process of evaluating the contingency plans of Changes.

Timing/trigger

Evaluate contigency plans at the following points in the release schedule:

Start of the mass rebuild
Branch day
Completion Checkpoint (Testable) deadline
Completion Checkpoint (100% complete) deadline
Start of Beta freeze
Start of Final freeze

In addition, if a Change has a different contingency deadline for whatever reason, evaluate plans then.

Process

In general, the process is to check with the owner and ask if the Change is on track. If not, work with them to defer it.

The two "change completion checkpoint" milestones on the schedule have specific actions.

Report incomplete Changes

This part of the process runs at the "Completion deadline (testable)" and "Completion deadline (100% complete)" milestones of the release schedule.

On the deadline day, use the fedora_bz.py script to comment on bugs that block the Changes tracking bug that do are not at least as far as MODIFIED (testable deadline) or ON_QA (100% complete deadline).
1. For the testable deadline, run e.g. ./fedora_bz.py deadline-testable 2024-02-20 40, where 40 is the release number and 2024-02-20 is the 100% complete deadline date (NOT the testable deadline date - this date is needed because the comment mentions it).
2. For the 100% complete deadline, run e.g. ./fedora_bz.py deadline-complete 40, where 40 is the release number. No date is needed here.
The next day, create a FESCo issue using one of the FESCo issue templates below. You may choose to try to figure out if a change is complete yourself, but you are not obligated to.
Continue to update the FESCo issue as bugs are updated.
Update or defer Changes as voted by FESCo.

Completion deadline (testable) FESCo issue template

On Tuesday, <DATE> we reached the Change Checkpoint: Completion deadline (testable). At this milestone all the F<VERSION> Changes should be testable, which is indicated by "MODIFIED" status of a tracking bug. A [Bugzilla query](pass:[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&f1=blocked&list_id=12817824&o1=substring&v1=F<VERSION>Changes]) shows all the tracking bugs which are not in "MODIFIED" state and are not considered testable. System-Wide Changes with the contingency date in bold are past the stated contingency date.

These changes are presented for FESCo review to determine what action, if any, should be taken. The next deadline is <DATE> when all changes should be 100% code complete.

## System-Wide Changes

* [<Change title>](<Wiki URL>)
    * Owner: @<ID>
    * Contingency mechanism: <mechanism>
    * Contingency deadline: <deadline>
* <repeat as necessary>

## Self-Contained Changes

* [<Change title>](<Wiki URL>)
    * Owner: @<ID>
* <repeat as necessary>

Completion deadline (100% complete) FESCo issue template

On Tuesday, <DATE> we reached the Change Checkpoint: Completion deadline (100% complete). At this milestone all the F<VERSION> Changes should be fully complete, which is indicated by "ON_QA" status of a tracking bug. A [Bugzilla query](pass:[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&f1=blocked&list_id=12817824&o1=substring&v1=F<VERSION>Changes]) shows all the tracking bugs which are not in "ON_QA" state and are not considered complete. System-Wide Changes with the contingency date in bold are past the stated contingency date.

These changes are presented for FESCo review to determine what action, if any, should be taken.

## System-Wide Changes

* [<Change title>](<Wiki URL>)
    * Owner: @<ID>
    * Contingency mechanism: <mechanism>
    * Contingency deadline: <deadline>
* <repeat as necessary>

## Self-Contained Changes

* [<Change title>](<Wiki URL>)
    * Owner: @<ID>
* <repeat as necessary>

Want to help? Learn how to contribute to Fedora Docs ›