Andriy Redko

> @andrross /@reta do you think we can use Changelog for this ? We probably would have to, but what are other breaking changes to mention? I think @nknize is...

@andrross I think we should track it, thanks!

> @reta -- is this a good place to build a wishlist for breaking changes in 3.0? Do you know if we have an existing good place to do that?...

> Another major update: [apache/lucene#13337](https://github.com/apache/lucene/pull/13337) Thanks @jed326 ! https://github.com/opensearch-project/OpenSearch/issues/11415 would be a better place to mention it I think, thanks!

@dblock would you mind if I submit a small patch for 1.3.x+ so it could be run on JDK 18? Thank you PS: To clarify why, JDK 18 is scheduled...

Thank you very much, @rmuir > I think the issue is written up correctly. You'll want to set -Djava.security.manager=allow from startup scripts (e.g. .bat/.sh), and from gradle when running tests?...

Thanks @rmuir , I think the large part with respect to "what the replacement should be" is still unknown, as it is dictated by Project Loom that is not there...

@Pallavi-AWS the recent (one of many) discussions on OpenJDK mailing list hint there won't be replacements for `SecurityManager` (very likely, at least) as well as there won't be suitable mechanisms...

Thanks @rmuir, hardening `systemd` would make sense in any case, w/o JSM, may be you could create an issue for that for OpenSearch? We also have to support Windows and...

> > We also have to support Windows and other distributions / platforms where systemd is not available, so it leaves us mostly with JSM only (for now at least)....