Adrian Bunk wrote:
> Easiest for security support would be keeping Redis/trixie with
> identical licence (and with a closer codebase) to Valkey, and
> then treat Valkey as upstream for Redis/trixie security support.
I see your point. I think we are simply comparing the subjective
difference between being able to apply the same patch for Valkey for
both Valkey and against the (old) version of Redis in trixie, versus
applying a Valkey patch against Valkey and a Redis patch against Redis.
I will note that Redis are releasing fairly nice stable point releases
similar to how Django does it. Indeed, 8.0.2 was released earlier
today, and it would be nice if we could release these updates via
security or pu. Obviously, we would not be able to do this if we
shipped 7.0.15 in trixie — a version, I should also add, that Redis
users will likely be warned away from using by upstream and others
(:/).
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
