Skip to content
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

Closed
marcwrobel opened this issue Nov 28, 2022 · 4 comments
Closed
Labels
request Request for a new tool or changes

Comments

@marcwrobel
Copy link
Member

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 ?

@marcwrobel marcwrobel added the request Request for a new tool or changes label Nov 28, 2022
@marcwrobel
Copy link
Member Author

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
...

@marcwrobel
Copy link
Member Author

Thought about it a little bit and this has some advantages but also disadvantages.

Advantages:

  • one page to track all the products
  • less maintenance from endoflife.date contributors

Disadvantages:

  • no link to changelog (each product has its own changelog)
  • less explanations about the product on the page (there is a lot of products and I suppose we do not want to have a huge product page)

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 ?

@marcwrobel
Copy link
Member Author

marcwrobel commented Dec 18, 2022

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.

@captn3m0
Copy link
Member

+1 to separate pages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request Request for a new tool or changes
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants