Accelerating the JDK release cadence

[Martijn Verburg]

Exactly this.  Even if the uptake of developers applying modularity to
their own applications is a little slow, Jigsaw is still proving it's worth
many, many times over by enabling incubation modules and an enhanced
@Deprecation system.  It's truly going to allow Java to develop at a rapid
pace in a *safe* manner, the best of both worlds.

This probably hasn't been said enough, but Mark, Alan and the rest of the
Jigsaw folks - I really appreciate the work that you've done to help
accelerate Java and give it longevity.

Cheers,
Martijn

On 8 September 2017 at 07:33, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> On 07/09/2017 20:04, cowwoc wrote:
>
>> While I like the idea of more frequent releases, I see two problems with
>> the
>> proposal in its current form:
>>
>> 1. It takes longer than 6 months for users to expose design problems.
>> Consider tagging new features with @Beta annotations, allowing the
>> breaking
>> of backward compatibility for another year or so, and eventually
>> graduating
>> them to stability by removing the @Beta tags.
>>
>> There is already support for incubating modules [1], also
> -XX:+UnlockExperimentalVMOptions to enable experimental options in the
> VM, and a few other mechanisms. In addition, if open build+test
> infrastructure can be established then it will should make it a lot easier
> for projects here to publish EA builds and should get more feedback around
> a feature while it is in development rather years after it has shipped.
>
> -Alan
>
> [1] http://openjdk.java.net/jeps/11
>