Thanks Michael,
Quite illuminating, I'd tend to wait for Java 11 (only 6 months from now) So it seems we will need to replace Java EE by Eclipse Jakarta, not sure
when yet, I guess before moving to Java 11
TL;DR: EE: http://openjdk.java.net/projects/jdk/11/
More at
https://dzone.com/articles/an-early-look-at-features-targeted-for-java-11
https://blog.takipi.com/java-11-will-include-more-than-just-features/
My 2cts
Jacques
Le 21/03/2018 à 22:45, Michael Brohl a écrit :
FYI: http://blog.joda.org/2018/02/java-9-has-six-weeks-to-live.html
Regards,
Michael
Am 31.01.2018 um 17:44 schrieb Taher Alkhateeb <slidingfilame...@gmail.com>:
I suspect that there is no difference between openjdk and oracle jdk as far
as the release cycle because oracle steers both.
However, like Jacopo I am not too concerned. The quick release cycle they
want to adopt means that there will be perhaps less drastic changes between
the versions.
I am open to changing our release cycle, but then we have to think
carefully about releases and more importantly we _must_ automate updates.
Something we can get ideas from is the upgrade package that a software
system like suitecrm provides to allow users to upgrade with a click.
However, I prefer sticking with our release cycle until we have a complete
idea of how to proceed.
On Jan 31, 2018 5:41 PM, "James Yong" <jamesy...@apache.org> wrote:
Hi all,
Not sure if this is workable.
Can we do open-source development against OpenJDK using a version that is
close to an Oracle JDK with LTS? Customers can choose the corresponding
Oracle JDK with LTS in production if they want to.
Regards,
James Yong
On 2018/01/29 16:21:50, Michael Brohl <michael.br...@ecomify.de> wrote:
Hi devs,
this is just an initial information and dicussion starter to make
everyone aware of this:
the Oracle Java release model is changing from a feature based to a time
based model [1]. One major drawback is that there will be no more public
patch releases for older versions once a new release is published, if I
understand correctly.
We'll have to discuss if this affects the project in terms of support
for the latest public Java releases. If we want to stay up-to-date
according to the public releases, we'll have to establish a process to
early check the new features and changes of a coming release and maybe
release more often.
We might even have to support the latest Java release along with the
current LTS release to cover both users with and without commercial
support? I'm not sure.
What do you think?
Best regards,
Michael
[1] https://www.azul.com/java-stable-secure-free-choose-two-three/
