epository" says:

<quote>
Users are recommended to begin transitioning their use of Redis to 
Valkey as soon as possible to avoid possible complications after the 14 
day transition window closes.
</quote>

   For other Arch packages that are configured to use redis (or 
php-legacy-redis), will the maintainers update the configs for the next 
release within the 14 day transition window?

   Or does "Users are recommended ..." mean just that, users need to try 
and make the replacements in all needed config files during the 14 days? 
I'm referring to packages like Nextcloud that Arch packages and has 
config files with entries for redis and php-legacy-redis. (with 
corresponding instructions in the Arch-wiki for Nextcloud)

   Also will there be corresponding php-valkey and php-legacy-valkey 
packages to replace the php-redis ones?

   The valkey docs are fairly clear, valkey is a for of redis 7.2:

https://valkey.io/topics/migration/

so other than a name change and change to start valkey instead of redis, 
is there anything else involved for the likes of Nextcloud? I don't have 
enough cache to worry about migration files from redis to valkey other 
than stopping/disabling redis, starting valkey and then reloading with 
the config file(s) name changed.

   So if there are no caches a user needs to migrate from redis, other 
than the redis package changing to valkey, will all other Arch packages 
that use redis be updated in this 14 day period?

-- 
David C. Rankin, J.D.,P.E.Valkey to replace Redis - Are devs updating configs in dependent packages (Nextcloud, etc..) to use valkey?David C Rankin <drankinatty@gmail.com> undefinedarch-general@lists.archlinux.org undefined¥)‚ž