You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we read the elasticsearch eol page then it states the following:
B) Subject to the periods set out in A), Elastic will provide Maintenance to the most recent two Minor Releases of the then-current Major Release, and the final Minor Release of the previous Major Release.
E.g., If version 2.8 is the most-current Minor Release, both 2.8 and 2.7 will receive Maintenance; and if 1.15 was the final Minor from the 1.x Major Release, and that Major Release is within its Maintenance Term, 1.15 would also receive Maintenance, whereas 1.14 would not.
Details of incorrect and correct details you have found
the project supports both 8.17 and 8.16 as of now or whatever is the last two release in 8.x series. meaning the support is based on last two minor versions whereas endoflife.date elasticsearch page only considers 8.x and 7.x (things based on major version)
I think we should track based on minor versions and should update it so that users know that both minor versions are supported in an active release window.
What is the source website for the product and for its version information?
This will also apply to the other Elastic products, right?
Yes looks like so especially for products under Core Stack which is listed over here. I think same is visible over https://github.com/elastic/beats/releases here as well where they release 8.17.x and 8.16.x at the same time during release.
Link to product page on endoflife.date
https://endoflife.date/elasticsearch
If we read the elasticsearch eol page then it states the following:
B) Subject to the periods set out in A), Elastic will provide Maintenance to the most recent two Minor Releases of the then-current Major Release, and the final Minor Release of the previous Major Release.
E.g., If version 2.8 is the most-current Minor Release, both 2.8 and 2.7 will receive Maintenance; and if 1.15 was the final Minor from the 1.x Major Release, and that Major Release is within its Maintenance Term, 1.15 would also receive Maintenance, whereas 1.14 would not.
Details of incorrect and correct details you have found
the project supports both 8.17 and 8.16 as of now or whatever is the last two release in 8.x series. meaning the support is based on last two minor versions whereas endoflife.date elasticsearch page only considers 8.x and 7.x (things based on major version)
I think we should track based on minor versions and should update it so that users know that both minor versions are supported in an active release window.
What is the source website for the product and for its version information?
For example: https://www.elastic.co/support/eol (point 2)
The text was updated successfully, but these errors were encountered: