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

Add the release blocking deliverables procedure

Browse source
This commit is contained in:
Ben Cotton 2019-10-03 13:04:23 -04:00
commit 40b51902ed
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
modules/pgm_guide/pages/release_process.adoc
View file

@ -13,6 +13,9 @@ The document beyond that is in chronological order.
** xref:_release_day[Release day]
** xref:_eol_closure_reminder[EOL closure reminder]
** xref:_eol_day[EOL day]
* *Deliverables*
** xref:_release_blocking_deliverables[Release blocking deliverables]
** xref:_spins_keepalive[Spins keepalive]
TIP: You may choose to create a https://fedoraproject.org/wiki/Releases/31/HouseKeeping[wiki page] to track the status of housekeeping tasks, as has been done historically.
@ -42,6 +45,15 @@ to help.
The process was re-approved by FESCo https://pagure.io/fesco/issue/1096 .
....
== Release blocking deliverables
Some deliverables are release blockers — we do not ship the release if they are not successfully composed.
FESCo approved a https://pagure.io/fesco/issue/2108[proposal] to use a static list of release-blocking deliverables.
Formerly, this was a manual audit process each release.
A week before the branch point, create the release-blocking page in the wiki (see https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking[the F31 page as an example]).
Email this to the devel mailing list. Any edits should have been included in Change proposals, but it's a good opportunity to catch anything that got overlooked.
== Branch Day
=== Update product description