10:24 p.m.
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
9:21 a.m.
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?
https://fedoraproject.org/wiki/EPEL_Updates_Policy#Stable_Releases
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
9:47 a.m.
On Fri, 16 Oct 2015 08:21:56 -0600
Orion Poplawski <orion(a)cora.nwra.com> wrote:
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?
https://fedoraproject.org/wiki/EPEL_Updates_Policy#Stable_Releases
And the section after that...
Some of the questions you should ask are:
* Does this update require manual end user changes? ie, config files,
or database formats or anything?
* Is the 2.4 stream still supported by upstream?
* If not are there security or other serious bugs that would make
moving to 2.8 desireable?
kevin
4:50 a.m.
* 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
8:48 a.m.
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.
2:35 a.m.
On 10/18/15, Haïkel <hguemar(a)fedoraproject.org> 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 2.8 is not easier than 2.4 to 3.0
Migration from users can't be avoided I think, and I doubt if there
are users using 2.4 since it's not supported and (may) full of
security holes.
--
Yours sincerely,
Christopher Meng
http://awk.io
10:12 a.m.
2015-10-20 9:35 GMT+02:00 Christopher Meng <i(a)cicku.me>:
On 10/18/15, Haïkel <hguemar(a)fedoraproject.org> 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 2.8 is not easier than 2.4 to 3.0
Migration from users can't be avoided I think, and I doubt if there
are users using 2.4 since it's not supported and (may) full of
security holes.
Yes, that's *exactly* what I was telling you. Skip 2.8 and update EPEL
branch straight to 3.0.x
H.
3111
days inactive
3115
days old
epel-devel@lists.fedoraproject.org
6 comments
4 participants
participants (4)
-
Christopher Meng -
Haïkel -
Kevin Fenzi -
Orion Poplawski