Redis-6 is currently shipped in EPEL9, so it seems like a more obvious step-forward wrt EPEL. > Honestly trying to replace redis with KeyDB in Fedora would be a step > backwards and cause headaches so I don't think it's feasible, at least > until redis v7 features are merged into KeyDB. Unfortunately, it's still the best option we have. Ideally, redis wouldn't have done this, but since redis is no longer license compatible, can we really continue to ship redis-7 in Fedora 40 if we can't patch and maintain it? If KeyDB were to merge and release a v7 version against the latest BSD code, I agree that it would be a much better target for Fedora 40. Unfortunately, we're in the awful position of having to choose between a breaking change for a small amount of users or shipping something that we can't patch or realistically maintain. If we have some clue that a v7 merge/release is on the very near horizon for KeyDB, then maybe it makes sense to keep redis and obsolete it for KeyDB after GA, but it would be preferable, IMO, to have a clean break on Fedora 40 release if possible, which will also give us a better chance to document it so the small amount of impacted end-users wrt v7-specific things can prepare for it. -- _______________________________________________ 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
