I’d particularly appreciate opinions on this (my original typos corrected):
> Discuss propriety of running convert2yaml.py on records.config as part of post-install script If this is not done by the %post scriptlet, the trafficserver unit will fail on an upgrade to 10.x, which seems less than ideal. On the other hand, if a no-longer-supported feature is used, even with an automatic update the unit will fail (but this is far less likely). It ends up being an unplessant choice between "always break" or "sometimes break". Is there general Fedora guidance on such things? --Jered On Fri, Jan 10, 2025 at 2:37 PM Aoife Moloney via devel-announce < devel-annou...@lists.fedoraproject.org> wrote: > Wiki - > https://fedoraproject.org/w/index.php?title=Changes/Trafficserver_10.0 > Discussion thread - > > https://discussion.fedoraproject.org/t/f42-change-proposal-trafficserver-10-0-self-contained/142034 > > This is a proposed Change for Fedora Linux. > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be implemented if approved > by the Fedora Engineering Steering Committee. > > == Summary == > Upgrade Apache Traffic Server in Fedora to version 10.0. > > == Owner == > * Name: [[User:jered| Jered Floyd]] > * Email: je...@redhat.com > > > == Detailed Description == > Apache Traffic Server in Fedora will be upgraded to v10.0. > > More details on Traffic Server 10.x are available from > [ > https://docs.trafficserver.apache.org/en/latest/release-notes/whats-new.en.html > the upstream What's New page]. Notably, there is a breaking change in > configuration file format, as ATS 10.x changes records.conf to > records.yaml and does not support the previous configuration format. > Many additional parameter changes and removals are also documented in > [ > https://docs.trafficserver.apache.org/en/latest/release-notes/upgrading.en.html > the upstream Upgrading page]. > > == Feedback == > > > == Benefit to Fedora == > Fedora includes the latest version of ATS, which will also be proposed > for EPEL 10. > > == Scope == > * Proposal owners: > ** Upgrade trafficserver package to 10.x > ** DIscuss proprietary of running convert2yaml.py on records.config as > part of post-install script > > == Upgrade/compatibility impact == > Users will be upgraded to Traffic Server 10.x. Daemon will not start > until records.config is updated to records.yaml. > > == How To Test == > Install package, or upgrade from older release. Configure, or update > configuration, then verify operation. > > == User Experience == > The user must update records.config to records.yaml before > trafficserver will restart after upgrade. > > Alternatively, this could be triggered as a post-install scriptlet. > In most cases the daemon would run normally after upgrade, as long as > no removed features are in use (see upstream documentation). > > == Dependencies == > None outside of this Change. > > == Contingency Plan == > > * Contingency mechanism: Roll back the trafficserver packages. > * Contingency deadline: Beta freeze > * Blocks release? No. > > == Documentation == > N/A (not a System Wide Change) > > == Release Notes == > Apache Traffic Server (trafficserver) in Fedora has been upgraded to > version 10.x. This introduces a breaking configuration change where > records.config must be updated to records.yaml. Additional upgrade > steps may be required if removed features or APIs are in use; please > review the upstream documentation at > > https://docs.trafficserver.apache.org/en/latest/release-notes/upgrading.en.html > > > -- > Aoife Moloney > > Fedora Operations Architect > > Fedora Project > > Matrix: @amoloney:fedora.im > > IRC: amoloney > > -- > _______________________________________________ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to > devel-announce-le...@lists.fedoraproject.org > 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-annou...@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
