Date: Thu, 12 Mar 2026 14:57:56 +0000 From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 293746] ELK 2026 Q1: consolidated PR for: Deprecate 7.x, Update 8.x, Add 9.x Message-ID: <bug-293746-37421-2vAcKNff5r@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-293746-37421@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293746 --- Comment #5 from Vladimir Druzenko <vvd@FreeBSD.org> --- (In reply to Saro from comment #4) Thanks. Updated list: - textproc/elasticsearch7 - sysutils/logstash7 Both: EoL 15 Jan 2026: Update 7.17.11 to last 7.17.29 and deprecate with EXPIRATION_DATE=2026-06-30, this PR - sysutils/beats8: Update 8.14.3 => 8.19.12, bug #290094 - textproc/elasticsearch8: Update 8.11.3 => 8.19.12, bug #288653 - textproc/kibana8: 8.19.12 is up to date, bug #289759 - sysutils/logstash8: Update 8.19.9 => 8.19.12, no PR - sysutils/beats91: New port 9.1.10, bug #291018 - sysutils/beats92: New port 9.2.6, bug #291019 - sysutils/beats93: New port 9.3.1, bug #293759 - textproc/elasticsearch9: New port 9.2.4 (why not 9.3.1?), bug #290954 - textproc/kibana9: New port 9.3.1, bug #290979 - sysutils/logstash91: Update 9.1.9 => 9.1.10, no PR - sysutils/logstash92: Update 9.2.3 => 9.2.6, no PR - sysutils/logstash93: New port 9.3.1, bug #293760 You know ELK stack better - can you write what are the next PRs (1-2-3) we should work on and commit? P.S. I took on all these ports because I see that the elastic@ group has been completely inactive for at least the last six months. I'm not a member of this group. However, due to the group's inactivity and the importance of the ELK stack, I believe it's acceptable to commit updates and new ports without waiting for approval from group members or a two-week timeout. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293746-37421-2vAcKNff5r>