From 855b4b8f4661ba99bc22c7605359878b442fbac0 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Nov 15 2024 19:23:15 +0000 Subject: Rawhide/branched composes are faster now, update MM links Signed-off-by: Adam Williamson --- diff --git a/releases/modules/ROOT/pages/branched.adoc b/releases/modules/ROOT/pages/branched.adoc index d7333e6..6b012f2 100644 --- a/releases/modules/ROOT/pages/branched.adoc +++ b/releases/modules/ROOT/pages/branched.adoc @@ -64,9 +64,9 @@ If any release-blocking image fails to build as part of the compose, the compose If the compose completes successfully, a set of automated tests intended to check its compliance with the https://fedoraproject.org/wiki/Basic_Release_Criteria[Basic Release Criteria] are run. If these tests pass, the compose will be synced out to the mirror system. Note that during https://fedoraproject.org/wiki/Milestone_freezes[freezes] there will be many days where 0 packages are added to the compose. -The Branched tree is under the next release's number on the mirrors. -You can find a local mirror on the http://mirrors.fedoraproject.org/publiclist/Fedora/[public mirror list]. -Compose time varies depending on number of changes, but is typically between 5 and 8 hours. +The Branched tree is under `development/branched` on the mirrors (when it exists). +You can find a local mirror on the https://mirrormanager.fedoraproject.org/mirrors/Fedora/development[public mirror list]. +Compose time varies depending on number of changes, but is typically between 2 and 3 hours. Branched is subject to various policies during its life cycle. For most of its existence, it is subject to the xref:fesco::Updates_Policy.adoc[Updates Policy] and package updates for it are gated through the https://fedoraproject.org/wiki/Bodhi[Bodhi] package review process. diff --git a/releases/modules/ROOT/pages/rawhide.adoc b/releases/modules/ROOT/pages/rawhide.adoc index 6f26ce4..6f00157 100644 --- a/releases/modules/ROOT/pages/rawhide.adoc +++ b/releases/modules/ROOT/pages/rawhide.adoc @@ -73,7 +73,7 @@ If the compose completes successfully, the compose will be 'synced out' to the m (A system where the sync only happens if a set of automated tests run on it passes is planned, but not yet fully implemented). Rawhide is under `development/rawhide` on the mirrors. -You can find a local "development" mirror on the http://mirrors.fedoraproject.org/publiclist/Fedora/development/[public mirror list]. Compose time varies depending on number of changes, but is typically between 5 and 8 hours. +You can find a local "development" mirror on the https://mirrormanager.fedoraproject.org/mirrors/Fedora/development[public mirror list]. Compose time varies depending on number of changes, but is typically between 2 and 3 hours. Composes are done in a rawhide chroot using the 'pungi' tool called from https://pagure.io/pungi-fedora/blob/main/f/nightly.sh[a script maintained by Fedora Release engineering]. If the base set of packages in Rawhide needed to compose Rawhide are broken, the daily compose may fail.