On Wed Dec 14, 2022 at 15:45 +0100, Miro Hrončok wrote: > Hello folks. > > A new major version of tox was released. The bump form version 3 to > version 4 > should be flawless to users but breaks all the plugins that have not > been > updated to the new API yet. > > I would like to avoid the need to maintain tox 3 in EPEL9 for many > years after > upstream abandoned it (they have no intention to do maintenance > releases for > tox 3.x). > > We are currently upgrading to tox 4 in Fedora Rawhide. When the dust > settles > I'd like to have the possibility to update it in EPEL too. > > One way to do it is to package a new tox4 component in EPEL 9 (and make > it > conflict with tox < 4) and keep the old tox around until it breaks (the > breakage might mean it no longer supports a newly added Python version > being > added to RHEL 9). > > Is that a sensible approach for EPEL? > There's no policy against compat packages in EPEL, so I see no problem with adding a tox4 component. We also have the EPEL Package Retirement policy[1] that allows you to retire packages as long as you announce it on the mailing list. BTW, we are currently discussing a slight change to this policy[2]. It'd be a good idea to decide on a retirement date in advanced for tox 3 and announce it on epel-announce. From there, you'd have to decide whether to completely retire the tox component and keep tox4 or to preform an Incompatible Update[3] of the tox package. This would require approval from the EPEL Steering Committee. Perhaps we can retire tox and have tox4 Provide tox but not Obsolete it. This way, existing users' setups won't be updated and potentially broken without explicit action, but new setups won't get unsupported content. You should open a ticket on the pagure.io/epel tracker once you have a concrete proposal. [1]: https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/ [2]: https://pagure.io/epel/pull-request/213 [3]: https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ -- Maxwell G (@gotmax23) Pronouns: He/Him/His _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
