Redis 5.0.5 when is end-of-life

[gosa...@gmail.com]

Hi All

We upgraded Redis in our production systems to Redis 5.0.5 in July 2019.   

(1) We are trying to find when is end-of-life for Redis 5.0.5

(2) How to find end-of-life of any Redis 5.0.x version?

(3) How to find end-of-life of any Redis 6.0.x version?  

Thanks

Sachin

[Matt Palmer]

On Fri, Jan 08, 2021 at 11:37:58PM -0800, gosa...@gmail.com wrote:
> We upgraded Redis in our production systems to Redis 5.0.5 in July 2019.
>
> (1) We are trying to find when is end-of-life for Redis 5.0.5

What do you mean by end-of-life?

- Matt

[Sachin Goyal]

"End of Life" is general term that is normally used in software industry to declare that after this time from the release date of a version, no fix-requests will be entertained, isn't it? 

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/redis-db/20210110221143.h3d7loikoco3hdrg%40hezmatt.org.

[Itamar Haber]

Hi Sachin,

For some context to my answer, I invite you to look at the draft document at https://github.com/redis/redis-doc/pull/1491.

That said, in my opinion, "End of Life" takes a different meaning in open source in general, and with Redis in particular. Please allow me to explain.

First, because Redis is totally OSS, you are free to apply/backport changes/fixes to whichever version you choose. The source code for all historical releases is always available at https://download.redis.io. This is unlike closed-source software where you have to rely on the vendor to maintain the version - in OSS you're welcome to do it yourself. I'm not necessarily suggesting that you want to do that, but you can if you must :)

Next, I'd like to make the claim that Redis specifically is quite stable (historically and that kind of being one of the underlying principles of its developers) both operationally as well as API-wise. That means that even old versions are extremely stable and can be (and are) used almost forever. That said, newer versions are usually better (given fixes and optimizations) and we try hard to ensure application-level compatibility while minimizing any operations-related impacts due to upgrades. The approach provides both stability as well as an easier upgrade path.

Lastly, perhaps, Redis is developed by (mostly) responsible professionals. Following the draft I shared above, Redis 5.0 (currently at 5.0.10) will continue receiving major fixes at least until the GA of Redis 7.0. Ideally, this would be towards mid/end of this year. That said, timing is everything and the unexpected can happen, so I'm not ruling out a scenario where a critical bug fix is shipped for 5.0 after that time. That would really depend on community inputs and the context.

I hope this helps in clearing some of the confusion and makes sense. If possible, it would be great if you would share your requirements regarding supporting old versions and "end of life" and the concerns you may have regarding running the latest stable versions.

Cheers,

Itamar

[Sachin Goyal]

Thanks for the detailed response. It is very helpful. 

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/redis-db/c39bfabc-0664-480b-ac37-bbe86fceec36n%40googlegroups.com.