2015-10-20 9:35 GMT+02:00 Christopher Meng :
> On 10/18/15, Haïkel wrote:
>> Considering EPEL update policy, there's no argument not to skip 2.8
>> and upgrade to 3.0.
>> 2.8 will be dropped when 3.2 will be released (WiP), and migrating
>> from 2.4 to
* Versions lower than 2.8 had been dropped from supported lifecycle
for a long time.
* Backporting fixes to 2.4 doesn't make too much sense.
* Config change is needed
(https://raw.githubusercontent.com/antirez/redis/2.6/00-RELEASENOTES).
--
Yours sincerely,
Christopher Meng
http://awk.io
Considering EPEL update policy, there's no argument not to skip 2.8
and upgrade to 3.0.
2.8 will be dropped when 3.2 will be released (WiP), and migrating
from 2.4 to 2.8 is not easier than 2.4 to 3.0
Regards,
H.
___
epel-devel mailing list
On 10/15/2015 09:24 PM, Christopher Meng wrote:
Hi,
Redis in EPEL6 is pretty dated, I'd like to update it to the latest
2.x version but somehow I haven't done major update like this.
Is it allowed to update the package from 2.4 to 2.8 for new RHEL 6.x
like 6.8 release?
Hi,
Redis in EPEL6 is pretty dated, I'd like to update it to the latest
2.x version but somehow I haven't done major update like this.
Is it allowed to update the package from 2.4 to 2.8 for new RHEL 6.x
like 6.8 release?
Thanks.
--
Yours sincerely,
Christopher Meng
http://awk.io