Proposal: Newer version-string scheme for the Java SE Platform and the JDK (original) (raw)
mark.reinhold at oracle.com mark.reinhold at oracle.com
Thu Nov 2 15:52:49 UTC 2017
- Previous message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Next message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2017/11/2 8:35:45 -0700, Dave Franken <dwfranken at gmail.com>:
...
Am I right in assuming that the main difference between LTS and non-LTS is that fixes that fall in the interim, update or emergency category are backported to LTS versions, but not to non-LTS versions?
Not all fixes will be backported. Whether a fix from a later release is backported to an LTS release will depend upon the importance and risk of the fix.
So currently, 11 will be a LTS version, so if there is going to be a update of non-LTS version 12.0 to 12.1, there will also be an 11.1, but not a 10.1?
No. JDK 11 will be an LTS release. Fixes from later releases, of any type, may be backported to JDK 11 update releases (11.0.1, 11.0.2, ...). If a fix in JDK 12.0.$N is backported to a JDK 11 update release then the version number of that update release need not be 11.0.$N.
There will never be a JDK 10.1, 11.1, or 12.1 with the six-month release model, but there could be at some point in the future if we revise the model again.
- Mark
- Previous message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Next message: Proposal: Newer version-string scheme for the Java SE Platform and the JDK
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]