operations/docs
operations/docs
3
0
Fork 4
Code Issues 2 Pull requests 1 Activity Actions

PGM guide changes contingency SoP: clarify a couple of points

Browse source 
This SoP said to "evaluate contingency plans" at four different
points, but only gave specific instructions for two. This tries
to add some kind of idea of what to do at the other two.

Also, we tweak the list of points to clarify that some of them
are on the same day in the current schedule.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2026-02-02 10:12:35 -08:00 • committed by Justin Wheeler
commit 4776bbad86
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
modules/ROOT/pages/pgm_guide/sop/changes-contingency.adoc
View file

@ -7,10 +7,8 @@ This document describes the process of evaluating the contingency plans of xref
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
* Completion Checkpoint (Testable) deadline / Branch day (currently the same day)
* Completion Checkpoint (100% complete) deadline / Start of Beta freeze (currently the same day)
* Start of Final freeze
In addition, if a Change has a different contingency deadline for whatever reason, evaluate plans then.
@ -20,7 +18,9 @@ In addition, if a Change has a different contingency deadline for whatever reaso
In general, the process is to check with the owner and ask if the Change is on track.
If not, work with them to xref:pgm_guide/sop/changes-defer.adoc[defer it].
The two "change completion checkpoint" milestones on the schedule have specific actions.
On the mass rebuild day, check for Changes that do not appear to be progressing, and informally remind the owner of the upcoming deadlines.
The two "change completion checkpoint" milestones on the schedule have specific actions below.
At the Final freeze, do a final check for still-unresolved incomplete Changes and ask FESCo to address them.
=== Report incomplete Changes