-
-
Notifications
You must be signed in to change notification settings - Fork 803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Elasticsearch and Filebeat by a single "Elastic suite" product #1928
Comments
See also : #1305. This new page will have alternate URLs for redirecting current products page to the new page : alternate_urls:
- /elasticsearch
- /logstash
- /filebeat
- /kibana
... |
Thought about it a little bit and this has some advantages but also disadvantages. Advantages:
Disadvantages:
So @endoflife-date/everyone, what should we do about the Elastic Suite ? Should we track each product separately or should we track all the products on a single page ? |
After having thought about it more I think it is best to track each product individually. This is more work for us but this is more in line with endofline.date objective (tracking EOL of individual products). Will create issues for tracking other products. |
+1 to separate pages. |
Currently there is a product page for ElasticSearch (https://endoflife.date/elasticsearch) and Filebeat (https://endoflife.date/filebeat).
But Elasticsearch, Kibana, Logstash, Filebeat... are all part of the "Elastic Suite" and share the same version. So when the Elastic Suite 7.17.7 is released, it means there is a versions 7.17.7 for each product :
Should we replace ElasticSearch and Filebeat pages with a single page, Elastic stack, mentioning all those products ?
The text was updated successfully, but these errors were encountered: