On 7/5/22 17:03, Neal Gompa wrote: > On Sat, Jun 25, 2022 at 2:17 PM Vipul Siddharth > <siddharthvipul1@xxxxxxxxx> wrote: >> >> >> == Feedback == >> >> This change was previously submitted for Fedora 34 and feedback were >> collected in the following [https://pagure.io/fesco/issue/2516 FESCo >> ticket]. >> The 2 main feedback received are either addressed or in the process of >> being addressed. >> >> * FCOS should not trail behind the latest Major Fedora version: see >> [[https://fedoraproject.org/wiki/Changes/FedoraCoreOS#Major_Fedora_Version_release_Go/NoGo|Major >> Fedora Version release Go/NoGo criteria]] >> > > I don't feel this is sufficiently addressed. Why is it that the stable > stream can't be switched when all the other artifacts are released? > Why is it two weeks *after* GA? Fedora CoreOS is unique in that by default nodes are automatically updated. We let the exact content set that we are going to ship to our `stable` stream bake in our `testing` stream for ~two weeks. This allows people to find issues that we don't find in our CI and report them. We find CI is good, but there is no substitute for real workloads. The exact content set delivered as part of Fedora GA isn't available two weeks before GA date so it's hard for us to ship GA content in our `stable` stream on GA day and follow our current update model. We do have the `next` stream which does get updated often in the weeks before GA, but a significantly smaller set of users are running `next`. Dusty _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
