Re: Oracle Java release model changes and consequences for the project

[Michael Brohl]

Hi devs,

a quick heads up for this topic.



Java 11 EA is available [2] so we could start to test with it.





Another way would be to make a new branch which will support Java 11.

What do people think?

Best regards,

Michael Brohl
ecomify GmbH
www.ecomify.de

After following the release strategy and thinking more about it, I think that most users will go with a subscription model and subscribe for an LTS version. The costs are moderate [1] and I assume that few users will go through a repeating 6 month "early access - update - test - go live" circle for free Java versions. The latest Intellij Idea already has support for Java 11, I suppose that it will come for Eclipse Photon shortly also. I wonder if we should base the OFBiz 17.12 release on Java 8 or Java 11. We have no fixed release date yet so we might have time to do it. [1] http://www.oracle.com/technetwork/java/javaseproducts/overview/javasesubscriptionfaq-4891443.html

[2] http://jdk.java.net/11/




Michael Brohl
Geschäftsführer

Fon      +49 521 448 157-91
Fax      +49 521 448 157-99
Mobil    +49 160 3664918
Xing     xing.com/profile/Michael_Brohl
LinkedIn linkedin.com/in/michaelbrohl

Company and Management Headquarters:
ecomify GmbH, Gustav-Winkler-Str. 22, 33699 Bielefeld, Deutschland
Fon: +49 521 448157-90, Fax: +49 521 448157-99, www.ecomify.de

Court Registration: Amtsgericht Bielefeld HRB 41683
Chief Executive Officer: Martin Becker, Michael Brohl

Am 29.01.18 um 17:21 schrieb Michael Brohl:

Hi devs,









What do you think?

Best regards,

Michael

[1] https://www.azul.com/java-stable-secure-free-choose-two-three/

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.

smime.p7s
Description: S/MIME Cryptographic Signature