Version-string schemes for the Java SE Platform and the JDK

[Dave Franken]

I assume we have the proper testing procedures in place to ensure the stability of any release, not just the LTS versions, but maybe more so for the LTS versions.
This means that nothing gets released, LTS or non-LTS unless properly tested, right?

We could still release RC versions prior to LTS if we desperately want this feedback.

Dave Franken

-----Original Message-----
From: Andrew Haley [mailto:aph at redhat.com] 
Sent: donderdag 26 oktober 2017 11:02
To: Dave Franken <dwfranken at gmail.com>; 'Mario Torre' <neugens.limasoftware at gmail.com>; 'Stephen Colebourne' <scolebourne at joda.org>
Cc: jdk-dev at openjdk.java.net
Subject: Re: Version-string schemes for the Java SE Platform and the JDK

On 26/10/17 09:19, Dave Franken wrote:
> My proposal is that there should be some restraint in adding backwards incompatible features in non-LTS releases, for instance local type inference (JEP 286) and value types (project Valhalla).

That's a bad idea.  It'd be extremely useful to bake anew language features for some time before committing them to a LTS release.

--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671