Learn more about these different git repos.
Other Git URLs
Hello, I need to update some module streams EOL date. However I don't fully understand the consequences of setting the EOL in the middle of the supported release. (Do we have any documentation for that ?)
I maintain - among others - the mariadb module and it's streams: 10.3, 10.4, 10.5, 10.6, 10.7, 10.8 (and soon 10.9 and 10.10 will be added)
mariadb
10.3
10.4
10.5
10.6
10.7
10.8
10.9
10.10
Several circumstances: - my capacity - upstream EOL closing in - missing OpenSSL 3 patch lead to me being unable to maintain the 10.3 and 10.4 module streams in Fedora anymore.
I've composed an email to devel@ & users@ mailing list explaining the current state, informing the users and advising on to which version(s) to move. I plan to send it one we'll agree here on which EOL date to set.
I packed the latest upstream released and they just entered BODHI: MariaDB 10.3: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2022-0cd0202272 MariaDB 10.4: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2022-c58e1ae21e But beyond that I don't plan to touch the 10.3 and 10.4 module streams anymore.
If EOL is only informative, I would like to set EOL to now.
If EOL blocks an update from going through BODHI to stable release, I would like to set EOL to (now + 1 month)
If EOL blocks users from installing and using the module streams, I would like to set the EOL to same as F35 EOL. Since F35 is still supported, I'd guess the date as (F37 release date + 1 month). Which should be (18 October 2022 + 1 month) = 18 November 2022
--
The 10.3 & 10.4 module streams are not available in Fedora > 35, since they are not patched for OpenSSL 3.
Module name: mariadb Module streams: 10.3, 10.4 New EOL date: as described above
as described above
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
We talked about this at fedora stand up. CC: @ppisar
I know post EOL, git commits will be rejected.
I am not sure if pungi cares about it for composing... hopefully ppisar knows. ;)
I have no idea what everything EOL affects. I know only about dist-git pushes. Because packagers are unable to push to dist-git, further places (Koji, Bodhi, Pungi) are untested. I believe that Pungi does not consult EOLs. I hope that Koji rejects tagging the build. I know that DNF does not consult these EOLs stored in PDC.
There is no documentation for setting these EOLs other than in https://docs.fedoraproject.org/en-US/modularity/building-modules/fedora/adding-new-modules/#_repositories_and_stream_branches_existing_packages.
Contrary, Modularity has an experimental support for another EOLs on repository level, called "obsoletes" https://docs.fedoraproject.org/en-US/modularity/building-modules/fedora/module-obsoletes/. But its implementation in DNF is rudimentary: It needs to be explicitly enabled in DNF configuration and DNF only implements moving to a different stream (e.g. from an EOL mariadb:10.3 to maridb:10.8) on "dnf system-upgrade" and partially on "dnf upgrade". Because of this experimental status, it won't help you much.
Alright, thanks for the insight. Let's set the EOL for the 10.3 and 10.4 streams to the F35 expected EOL date.
EOL is now set for 10.3 and 10.4 to the EOL of Fedora 35.
https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?global_component=mariadb
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.