On 31-03-2024 00:41, Kevin Fenzi wrote:
On Sat, Mar 30, 2024 at 11:12:02PM +0100, Sandro wrote:
From what I understood, F40 Beta, the official Beta release, available from
the website as of March 26, has updates-testing disabled by default. That
Nope.
was confirmed by several people in #devel yesterday when the Fedora Magazine
article was still being worked on.
I am pretty sure I said the opposite...
nirik: Branched enables updates-testing... so if you installed f40 anytime, you will have it enabled and if you then applied updates it would be in them
nirik: yes, we disable updates-testing by default right before release.
I guess that could have been read as right before beta release, but
thats not the case or what I meant. ;)
It's before _Final_ release that we disable updates-testing.
It's enabled by default from when we branch the release off until the
time right before release when we switch it (usually with a freeze
break/blocker bug)
Thanks for clarifying that. Context matters and there was a lot going on
in the channel at the time. My wording was to the extend covering
composes before Beta was released. I used the the term "pre-Beta".
Good to know that the switch is made "pre-Final".
It's the RC composes that are made after branching and before Beta is
declared GO, that have updates-testing enabled by default. I was one of the
persons raising that point. I'm less certain wrt upgrades in the period
between branching and Beta release.
I think the confusion here is "Beta Release" vs "Final release".
Yup! I was thinking "Beta Release".
We enable updates-testing at branching time all the way until right
before "Final release". :)
If that is incorrect and Beta shipped with updates-testing enabled,
deliberately or by accident, then I stand corrected.
Yes, it did/does. :)
The logic is that most people who install betas or pre-releases want to
help test updates. If for some reason they don't, they can disable it,
but the default option is on.
That makes sense. I thought along the same lines as to why it is enabled
by default right after branching.
Thanks also to @adamwill and @pbrobinson for further
clarification/confirmation later on.
The following sentence in the magazine article:
"Fedora Linux 40 Beta users may have received it from the testing
repositories, which are enabled by default in branched versions (i.e.
pre-Beta) to assist with testing."
should probably be amended in the light of above. Though, most people
affected probably took measures already and new installations won't be
affected.
-- Sandro
--
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
