<div dir="ltr"><div dir="ltr"><div>Dealing with the second question (when do we bump the version post-JFX20),</div><br class="gmail-Apple-interchange-newline"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 19, 2022 at 10:39 PM Philip Race <<a href="mailto:philip.race@oracle.com">philip.race@oracle.com</a>> wrote:<br></div><div>... </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
What to do in future (ie what is the policy) is a separate question<br>
<br>
OpenJDK LTS releases will be every two years in future, so there is a <br>
reasonable argument that<br>
is too frequent to bump the FX minimum without a really compelling reason.<br>
<br>
Also consider that FX 20 will GA 4 1/2 years after FX 11 and the next <br>
JDK LTS will be 21 ..<br>
just 6 months later .. we surely aren't going to bump the minimum again <br>
immediately.<br>
<br>
So we should not have a policy of the "latest LTS" should always be the <br>
minimum - just that it should<br>
be "some" LTS<br>
<br>
And perhaps we skip every other LTS or at the very least we don't bump <br>
until the LTS has been available for 1 year ..<br></blockquote><div><br></div><div>A possible idea is to apply the following 2 rules:</div><div><br></div><div>1) Whenever we bump the JDK version in JavaFX, it should be bumped to a JDK LTS version that is at least 1,5 years (minus 1 week) old at JFX release date. This is exactly what will happen if the JFX 20 has a minimum JDK version of 17. This gives OpenJFX developers enough time to play with the new JDK features before using them in OpenJFX code. </div><div><br></div><div>2) We evaluate the options provided by the next LTS much in advance, and case by case (every 2 years), we discuss whether it is worth bumping the release (following rule 1)) . </div><div><br></div><div>- Johan</div></div></div>