We cannot upgrade Jetty if we stay on JDK11, which is my biggest concern about
it.
> On Aug 19, 2025, at 19:11, Christopher wrote:
>
> Sorry for the confusion. I linked that PR mostly for my own reference
> to review to make a new PR. You can ignore that PR for now. I would
> create a new on
I think most people interpret Java/maven version numbers (x.y.z) as:
x = major
y = minor
z = patch/bugfix
I think it's confusing when you say 3.10 is a "major" version. What would
you call 4.0.0? A "supremely major" release, perhaps? It's fine to treat a
minor release as a substantial change, but
Sorry for the confusion. I linked that PR mostly for my own reference
to review to make a new PR. You can ignore that PR for now. I would
create a new one for this. I was getting ahead of myself, because I
know that bumping the minimum build version would also include a bump
of the Apache parent PO
Okay. I checked the pull request that you linked and there’s a lot more in that
most of which I don’t even understand. I suggest the following:
- let’s finish that PR by adding minimum build version of JDK 11 for now,
- merge the PR to all active branches: master, branch-3.9 and branch-3.8,
- re
This is a release candidate for 3.9.4.
This is a minor release with bug- and security fixes. Important to note that
due to security issues we’ve upgraded logback to 1.3.15 and slf4j to 2.0.13. No
ZooKeeper code changes have been involved in this upgrade, but the SLF4j
upgrade was a major versio
Andor Molnar created ZOOKEEPER-4964:
---
Summary: Check permissions individually during admin server auth
Key: ZOOKEEPER-4964
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4964
Project: ZooKeeper
We agreed on that we cut 3.10.0 from the master branch as new major release of
ZooKeeper. There’s no plan for 4.0.0 right now.
Bumping minimum JDK version to JDK 17 is for 3.10.0 only.
I suggested JDK 17, because I’d like to do a major refactoring to upgrade Jetty
to the latest (12.1) version a
I have reservations about bumping the minimum runtime Java version to
17, because I have applications that use ZooKeeper client code that
run Java 11. I think a more modest change would be to bump the
required build version to 17, but keep the target version at 11. If
this is being considered for 4
Thanks for bringing my suggestion to the mailing list for discussion.
I wasn't aware that 17 was being considered. Is there another
discussion thread I can read about that?
My suggestion could apply with JDK 17 instead of 11. I didn't suggest
17 because I thought 11 would be more acceptable as a
