I understand. Jetty has been pretty aggressive at updating to jakarta and
newer Java versions. It's hard to keep Jetty up-to-date. What do you think
about just calling it 4.0 and skipping 3.10?
On Tue, Aug 19, 2025 at 9:14 PM Andor Molnar wrote:
> We cannot upgrade Jetty if we stay on JDK11, whi
It looks like that Confluence page is pretty close to Semver 2.0's
definition (semver.org).
I was confused by the use of the word "major" to refer to 3.10 earlier in
this thread. By the definition there, it'd be a "minor" release.
Since the version numbering is based on API changes, and not depend
FYI here's what documented for the project:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=24193438#Roadmap-ReleaseNumbering
I personally think about it along these lines: "Upgrading between major
releases will generally require changes to user code".
The "annually" - I guess that
Kezhu Wang created ZOOKEEPER-4968:
-
Summary: Introduce interface to cover ZooKeeper client operations
Key: ZOOKEEPER-4968
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4968
Project: ZooKeeper
Kezhu Wang created ZOOKEEPER-4967:
-
Summary: Builder to construct ZKConfig
Key: ZOOKEEPER-4967
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4967
Project: ZooKeeper
Issue Type: New Fea
Kezhu Wang created ZOOKEEPER-4966:
-
Summary: QuorumPeerConfig.ConfigException leaked to client side
code through constructor of ZKConfig
Key: ZOOKEEPER-4966
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-496
Kezhu Wang created ZOOKEEPER-4965:
-
Summary: Drop unnecessary {{@SuppressWarnings("deprecation")}}
Key: ZOOKEEPER-4965
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4965
Project: ZooKeeper
