Nitin,
The codehaus lists are incorrect, use the eclipse lists.
And don't use the announce lists for discussions or questions.
Back to your question ...
The Servlet and HTTP specs updated at a far faster rate than Eclipse Equinox, sorry.
First, a refresher on how we (Jetty) do versioning.
(Major.Minor.BugFixes)
Major is updated with Servlet spec releases (and to a lesser extend the Java minimums)
7 = Servlet 2.5 (Java 6)
8 = Servlet 3.0 (Java 7)
9 = Servlet 3.1 (Java 7 -> Java 8)
10 = Servlet 4.0 (Java 9)
Minor is updated when there is significant changes in our implementation or feature set.
9.0 = Beta Servlet 3.1 support
9.1 = Servlet 3.1 final, and introducing JSR-356 (javax.websocket) support
9.2 = Servlet 3.1 final, dropped OPTIONS from distribution, introduced jetty.home and jetty.base split, along with modules system
9.3 = Servlet 3.1 final, introduced HTTP/2 support along with EatWhatYouKill scheduling overhaul
Jetty 9 is Servlet spec 3.1, which has a Java 7 minimum.
Java 7 itself went EOL back on Apr 15th (this month).
Jetty 9.3 is already introducing Java 8 specific classes (currently to support optional SSL with SNI behavior)
Jetty 9.4 might be a Java 8 minimum.
Jetty 10 will start when Servlet 4.0 begins, and will most certainly will be at least Java 9.
Java 9 is the first version of Java scheduled for support with ALPN built-in.
ALPN is a requirement for HTTP/2
We support HTTP/2 on Jetty 9.3+, but currently with a -Xbootclasspath entry requirement to shoehorn in a replacement SSL layer that we maintain to add ALPN support to Java itself.
Since we maintain 2 active lines of Jetty right now, (Jetty 9.2 and Jetty 9.3) we have no desire to maintain a third, even older branch (Jetty 8), as the changes between them are just too great.
