Hi,
EPEL7 currently ship Redis 2.8.x branch, but it will be EOLed soon after the 3.2.x branch will be released. I plan to update EPEL7 branch to 3.0.x, there's no specific action required from users for the migration.
Regards, H.
On Mon, Feb 8, 2016 at 3:48 PM, Haïkel hguemar@fedoraproject.org wrote:
Hi,
EPEL7 currently ship Redis 2.8.x branch, but it will be EOLed soon after the 3.2.x branch will be released. I plan to update EPEL7 branch to 3.0.x, there's no specific action required from users for the migration.
Is there client side soname bumps which will need associated rebuilds for anything that depends on it?
2016-02-08 16:56 GMT+01:00 Peter Robinson pbrobinson@gmail.com:
Is there client side soname bumps which will need associated rebuilds for anything that depends on it?
redis does not provide any library or public API, clients use the wire protocol which remains compatible. No rebuilds required.
epel-devel@lists.fedoraproject.org