Assuming KeyDB gets accepted (it looks close from the Bugzilla review), we should obsolete redis for KeyDB in Fedora 40+ and consider eventually doing likewise with EPEL as well, since we aren't going to be able to ship any redis patches moving forward. I feel less strongly about that for EPEL as for Fedora. As a Fedora redis user, personally, having KeyDB in-place replace redis on upgrade to Fedora 40 seems like the best possible route moving forward to limit end-user disruption and technical debt for Fedora. As long as KeyDB's multi-threading isn't enabled out of box, it should essentially be equivalent to redis-6 as I understand it. We're currently shipping redis-7.2.4 in Fedora 39. Are there any potential redis-7 specific compatibility problems with KeyDB migration? -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
