operations/docs
operations/docs
3
0
Fork 4
Code Issues 2 Pull requests 1 Activity Actions
docs/modules/ROOT/pages/pgm_guide/sop/changes-contingency.adoc

82 lines
4.4 KiB
Text
Raw Permalink Normal View History

Split Changes SOP into multiple docs This makes it a lot easier to understand
2023-03-16 12:21:33 -04:00
= Changes (Contigency) SoP
This document describes the process of evaluating the contingency plans of xref:changes_policy.adoc[Changes].
== Timing/trigger
Evaluate contigency plans at the following points in the release schedule:
* Start of the mass rebuild
PGM guide changes contingency SoP: clarify a couple of points 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>
2026-02-02 10:12:35 -08:00
* Completion Checkpoint (Testable) deadline / Branch day (currently the same day)
* Completion Checkpoint (100% complete) deadline / Start of Beta freeze (currently the same day)
Split Changes SOP into multiple docs This makes it a lot easier to understand
2023-03-16 12:21:33 -04:00
* 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 xref:pgm_guide/sop/changes-defer.adoc[defer it].
PGM guide changes contingency SoP: clarify a couple of points 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>
2026-02-02 10:12:35 -08:00
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.
Split Changes SOP into multiple docs This makes it a lot easier to understand
2023-03-16 12:21:33 -04:00
=== Report incomplete Changes
This part of the process runs at the "Completion deadline (testable)" and "Completion deadline (100% complete)" milestones of the release schedule.
Update fedora_bz.py usage for recent changes, add it for Changes I made some significant changes to the fedora_bz.py script today. This updates the docs to reflect current usage of the script after these changes. It also changes the changes-contingency page to recommend using the script - currently the page does not say to use the script even though it has the capability to do the necessary work for the change deadlines. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-11-22 17:43:17 -08:00
. On the deadline day, use the https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_bz.py[`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).
.. 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).
.. 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.
Split Changes SOP into multiple docs This makes it a lot easier to understand
2023-03-16 12:21:33 -04:00
. The next day, create a FESCo issue using one of the xref:#fesco-issue-templates[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.
'''
anchor:fesco-issue-templates[]
==== 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>
....
Reference in a new issue Copy permalink