Proposing Beta UT package set enable Release Criteria

[Sumantro Mukherjee]

Hey folks,

A few moons ago, I volunteered to write a Beta Release Criteria. The idea
is to set a "criteria"
to have Beta images with Updates Testing enabled by default. Note, we *do*
this and have been doing this for some time and nothing has broken badly
due to keeping UT repos enabled.
This IMO will encourage our community to try to test more Beta images and
package sets which will be served to them when they upgrade to Beta or
install beta from various installation sources.

Proposed Beta Criteria:

Release identification
A fedora-release package containing the correct names and information and a
fedora-repos package containing the correct repository configuration for a
Beta Fedora release must be present on release-blocking images and the
appropriately versioned generic-release package must be available in the
release repository.

updates-testing enabled
One specific expectation is that the updates-testing repository and any
corresponding repositories (e.g. updates-testing-modular) must be enabled
for upgrades to beta and fresh installs.

Please let me know your thoughts.

[Neal Gompa]

On Sat, Oct 5, 2024 at 1:36 PM Sumantro Mukherjee 
wrote:
> Hey folks,
>
> A few moons ago, I volunteered to write a Beta Release Criteria. The idea
> is to set a "criteria"
> to have Beta images with Updates Testing enabled by default. Note, we *do*
> this and have been doing this for some time and nothing has broken badly
> due to keeping UT repos enabled.
> This IMO will encourage our community to try to test more Beta images and
> package sets which will be served to them when they upgrade to Beta or
> install beta from various installation sources.
>
> Proposed Beta Criteria:
>
> Release identification
> A fedora-release package containing the correct names and information and
> a fedora-repos package containing the correct repository configuration for
> a Beta Fedora release must be present on release-blocking images and the
> appropriately versioned generic-release package must be available in the
> release repository.
>
> updates-testing enabled
> One specific expectation is that the updates-testing repository and any
> corresponding repositories (e.g. updates-testing-modular) must be enabled
> for upgrades to beta and fresh installs.
>
> Please let me know your thoughts.

This makes sense to me, I think they're perfectly reasonable criteria to
add.

[pmkellly]

Looks good to me.

Have a Great Day!

Pat  (tablepc)

On Sat, Oct 5, 2024 at 1:36 PM Sumantro Mukherjee 
wrote:
> Hey folks,
>
> A few moons ago, I volunteered to write a Beta Release Criteria. The idea
> is to set a "criteria"
> to have Beta images with Updates Testing enabled by default. Note, we *do*
> this and have been doing this for some time and nothing has broken badly
> due to keeping UT repos enabled.
> This IMO will encourage our community to try to test more Beta images and
> package sets which will be served to them when they upgrade to Beta or
> install beta from various installation sources.
>
> Proposed Beta Criteria:
>
> Release identification
> A fedora-release package containing the correct names and information and
> a fedora-repos package containing the correct repository configuration for
> a Beta Fedora release must be present on release-blocking images and the
> appropriately versioned generic-release package must be available in the
> release repository.
>
> updates-testing enabled
> One specific expectation is that the updates-testing repository and any
> corresponding repositories (e.g. updates-testing-modular) must be enabled
> for upgrades to beta and fresh installs.
>
> Please let me know your thoughts.
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED https://redhat.com/trusted
> --
> _______________________________________________
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Derek Enz]

Yes sounds good to me!

Derek Enz

On Sat, Oct 5, 2024 at 10:40 AM pmkellly  wrote:
> Looks good to me.
>
> Have a Great Day!
>
> Pat  (tablepc)
>
> On Sat, Oct 5, 2024 at 1:36 PM Sumantro Mukherjee 
> wrote:
> > Hey folks,
> >
> > A few moons ago, I volunteered to write a Beta Release Criteria. The idea
> > is to set a "criteria"
> > to have Beta images with Updates Testing enabled by default. Note, we
> > *do* this and have been doing this for some time and nothing has broken
> > badly due to keeping UT repos enabled.
> > This IMO will encourage our community to try to test more Beta images and
> > package sets which will be served to them when they upgrade to Beta or
> > install beta from various installation sources.
> >
> > Proposed Beta Criteria:
> >
> > Release identification
> > A fedora-release package containing the correct names and information and
> > a fedora-repos package containing the correct repository configuration for
> > a Beta Fedora release must be present on release-blocking images and the
> > appropriately versioned generic-release package must be available in the
> > release repository.
> >
> > updates-testing enabled
> > One specific expectation is that the updates-testing repository and any
> > corresponding repositories (e.g. updates-testing-modular) must be enabled
> > for upgrades to beta and fresh installs.
> >
> > Please let me know your thoughts.
> >
> > --
> > //sumantro
> > Fedora QE
> > TRIED AND PERSONALLY TESTED, ERGO TRUSTED https://redhat.com/trusted
> > --
> > _______________________________________________
> > test mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
> --
> _______________________________________________
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Kevin Fenzi]

On Sat, Oct 05, 2024 at 11:05:46PM +0530, Sumantro Mukherjee wrote:
> Hey folks,
>
> A few moons ago, I volunteered to write a Beta Release Criteria. The idea
> is to set a "criteria"
> to have Beta images with Updates Testing enabled by default. Note, we *do*
> this and have been doing this for some time and nothing has broken badly
> due to keeping UT repos enabled.
> This IMO will encourage our community to try to test more Beta images and
> package sets which will be served to them when they upgrade to Beta or
> install beta from various installation sources.
>
> Proposed Beta Criteria:
>
> Release identification
> A fedora-release package containing the correct names and information and a
> fedora-repos package containing the correct repository configuration for a
> Beta Fedora release must be present on release-blocking images and the
> appropriately versioned generic-release package must be available in the
> release repository.

I guess spot has been keeping generic-release going, but I don't think
anyone from releng has been updating it. I guess it's not been a problem
tho...
> updates-testing enabled
> One specific expectation is that the updates-testing repository and any
> corresponding repositories (e.g. updates-testing-modular) must be enabled
> for upgrades to beta and fresh installs.

*modular* should be gone completely now, so drop mention of it?
> Please let me know your thoughts.

Seems fine. Thanks for writing this up.

kevin

[Sumantro Mukherjee]

On Sat, Oct 5, 2024 at 11:41 PM Kevin Fenzi  wrote:
> On Sat, Oct 05, 2024 at 11:05:46PM +0530, Sumantro Mukherjee wrote:
> > Hey folks,
> >
> > A few moons ago, I volunteered to write a Beta Release Criteria. The idea
> > is to set a "criteria"
> > to have Beta images with Updates Testing enabled by default. Note, we
>
> *do*
> > this and have been doing this for some time and nothing has broken badly
> > due to keeping UT repos enabled.
> > This IMO will encourage our community to try to test more Beta images and
> > package sets which will be served to them when they upgrade to Beta or
> > install beta from various installation sources.
> >
> > Proposed Beta Criteria:
> >
> > Release identification
> > A fedora-release package containing the correct names and information
>
> and a
> > fedora-repos package containing the correct repository configuration for
>
> a
> > Beta Fedora release must be present on release-blocking images and the
> > appropriately versioned generic-release package must be available in the
> > release repository.
>
> I guess spot has been keeping generic-release going, but I don't think
> anyone from releng has been updating it. I guess it's not been a problem
> tho...
> > updates-testing enabled
> > One specific expectation is that the updates-testing repository and any
> > corresponding repositories (e.g. updates-testing-modular) must be enabled
> > for upgrades to beta and fresh installs.
>
> *modular* should be gone completely now, so drop mention of it?

In that case Kevin, I will also have to update a few more places. Given
Adamw and Kamil agree :)
I might wanna change
https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria#Release_iden...
> > Please let me know your thoughts.
>
> Seems fine. Thanks for writing this up.

Thanks a lot for reviewing!
> kevin
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Kamil Paral]

On Sun, Oct 6, 2024 at 3:21 PM Sumantro Mukherjee 
wrote:
> *modular* should be gone completely now, so drop mention of it?
> >
>
> In that case Kevin, I will also have to update a few more places. Given
> Adamw and Kamil agree :)

I think it's fine to drop modular mentions in all places (there might be
some notes even in footnotes, but they can't be easily searched because
they are collapsed by default :-/ it's lame, but perhaps search in the html
source?). But it should be done as a separate edit, properly described in
the edit message, not grouped together with adding a new criterion or
similar.

[Kamil Paral]

On Sat, Oct 5, 2024 at 7:36 PM Sumantro Mukherjee 
wrote:
> Proposed Beta Criteria:
>
> Release identification
> A fedora-release package containing the correct names and information and
> a fedora-repos package containing the correct repository configuration for
> a Beta Fedora release must be present on release-blocking images and the
> appropriately versioned generic-release package must be available in the
> release repository.

This is basically a copy of the Final criterion, moved forward to Beta.
(That's not a problem, I'm just stating it). So technically your proposal
doesn't just mandate that updates-testing must be enabled, but also all the
other bits about system name and info and all repo config, etc. It sounds
OK to me, but I'd like Adam to confirm.

If the generic-release package is no longer considered important and
well-maintained (Kevin suggested something like that), perhaps we can drop
it from the criteria?
> updates-testing enabled
> One specific expectation is that the updates-testing repository and any
> corresponding repositories (e.g. updates-testing-modular) must be enabled
> for upgrades to beta and fresh installs.

"enabled for upgrades to beta" sounds like it needs to be enabled in the
FN-1 version when doing an upgrade to FN, for the process of the upgrade
itself. That's certainly not the case, and we don't even want it. I'd keep
the phrase the same as in the Final criterion, i.e. "the updates-testing
repository and any corresponding repositories must be enabled".

Upgraded systems are covered by a criterion that says that upgraded systems
must satisfy all criteria.

[Neal Gompa]

On Thu, Oct 10, 2024 at 7:09 AM Kamil Paral  wrote:
> On Sat, Oct 5, 2024 at 7:36 PM Sumantro Mukherjee  wrote:
> > Proposed Beta Criteria:
> >
> > Release identification
> > A fedora-release package containing the correct names and information and a fedora-repos package containing the correct repository configuration for a Beta Fedora release must be present on release-blocking images and the appropriately versioned generic-release package must be available in the release repository.
>
> This is basically a copy of the Final criterion, moved forward to Beta. (That's not a problem, I'm just stating it). So technically your proposal doesn't just mandate that updates-testing must be enabled, but also all the other bits about system name and info and all repo config, etc. It sounds OK to me, but I'd like Adam to confirm.
>
> If the generic-release package is no longer considered important and well-maintained (Kevin suggested something like that), perhaps we can drop it from the criteria?

I would rather it remain, and if it needs a new maintainer, I'd be
happy to do it.