fesco

#2139 F30: change default stream for avocado module
Closed: Invalid by zbyszek. Opened by merlinm.

Closed: Invalid
Reopen Issue

I would like to request changing the default stream for the avocado module in F30 from stable to 52lts. [1]

The avocado:stable stream name was chosen and made sense when there was only one upstream Long Term Stability release of Avocado [2] being represented as a module--which was Avocado 52.x LTS. However, when Avocado 69.0 LTS was released in February 2019, there were then two "stable" releases of Avocado to track. Thus, the 52lts stream was created as an exact duplicate of the existing stable stream, and a new 69lts stream was created.

To avoid confusion and provide clarity for users, I am proposing to change the default avocado module stream to 52lts for F30--while maintaining the existing stable default stream as an exact duplicate of the 52lts stream.

Note: the 52lts and stable streams will go away in F31 since Avocado 52.x LTS is Python 2-only.

[1] https://pagure.io/releng/fedora-module-defaults/pull-request/107
[2] https://avocado-framework.readthedocs.io/en/latest/rfcs/LongTermStability.html

I think DNF does not handle changing of default streams in any way, so if users would get different results when installing fresh f30 with new defaults than what they got before.. This needs to be taken into consideration.

I think Modularity WG decided to not allow changing default streams in released versions. But I'm definitely +1 to do it in rawhide.

avocado:69lts was already set as the default in Rawhide a few months back.

+1

Changing a default would affect only new installs. Modularity WG did agree some time ago that changing defaults in a stable release was not permitted.

DNF work is planned to allow changing defaults when upgrading between releases, but to the best of my knowledge, that's not finished yet.

-1 to this change on the stable branches. It's unfortunate, but please just keep the current one.

Given that stable users won't follow the change in default, I am also -1 (but agree that it would be nice if we had a way to do that in the future).

Given that stable users won't follow the change in default, I am also -1 (but agree that it would be nice if we had a way to do that in the future).

The current plan for tracking default changes will handle this (since we need to be able to deal with it on both distro upgrades and just at random in Rawhide). It's not available yet, though.

I have gone ahead and closed https://pagure.io/releng/fedora-module-defaults/pull-request/107 due to the current limitations.

Metadata Update from @zbyszek:
- Issue tagged with: meeting

Closing as withdrawn.

Metadata Update from @zbyszek:
- Issue untagged with: meeting
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.