-
Notifications
You must be signed in to change notification settings - Fork 34
stop publishing debian7 and debian8 from 1.23.7 onwards #510
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
Conversation
This pull request does not have a backport label. Could you fix it @v1v? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
You can get rid of debian8 for sure. 7.17 still references debian 7 but not 8 which is strange. Let me look into if we still need this as the support matrix has been updated since those changes. Main and 8.x are all using Debian 11. |
The Linux case selecting Debian 7 is the problematic one.
|
Thanks for double checking, I missed the I'll change the scope for Debian 8 in this PR for now, and then we can figure out if |
From https://www.elastic.co/support/matrix Several Beats like Packetbeat, Heartbeat, and Auditbeat claim to support Debian 8 in 7.17 with no footnotes. For Filebeat and Metricbeat there is a footnote that we only support Debian 10 and above. So we potentially can remove Debian 7 assuming it doesn't break compatibility with the glibc in the older RHEL releases we support. Or we can wait until 7.17.x goes EOL and do a larger removal of lots of things. |
Although Do we plan to support |
I wanted to take the opportunity to remove them before No rush in what we decide to do here. We can wait for |
We will probably leave 7.17 at 1.22 so that makes sense to me. |
Great, we have a plan, I'll merge this PR as is then - only after your review please |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
Closes #509
See