Conversation
|
Our file format currently only supports release dates, not EOL dates. Those are manually updated directly in the endoflife.date repository. We plan to add support for scraping EOL dates in this repo (#125), but that's still in planning. Till that, maybe we can change this to a separate |
|
🤦🏾 that makes sense, that was a misunderstanding on my part. Thank you. |
The goal is in my (current) opinion to have all the data in the same file because I find it easier to manage that way. So I would rather wait until it is supported. |
|
This is now possible, and for Redis it also maybe already natively supported through the Note that https://redis.io/docs/latest/operate/rs/installing-upgrading/product-lifecycle/ may be only valid for Redis Enterprise, and https://endoflife.date/redis seems to document the OSS version. So maybe it would be better to create a separate product ? |
+1. We should also add the Redis forks. I can't find good naming for the Source-Available Redis variant - we can't use "Redis Open Source". Maybe Redis Public/Community? |
|
Had a look and it turned out a custom script is not necessary anymore, see endoflife-date/endoflife.date#6730. |
Relates to endoflife-date/endoflife.date#3261.
Could you help me understand how the automation interacts with the existing
redis.jsonfile? There seems to be some unwanted deletions caused by the runningredis.py.Parses the End-of-life schedule from: https://docs.redis.com/latest/rs/installing-upgrading/product-lifecycle/