On Thu, 16 Mar 2023 at 11:46, Svata Dedic <[email protected]> wrote: > I see the rapid movement between > JDK versions that is even increasing with increased frequency of JDK > releases (with only limited features that make a real difference for NB > development) as dangerous
But also a reality we don't control, and affects not just us but the ecosystem we rely on. > In my current state of mind / evaluation of the issue I'd give -0.5 to > JDK8 drop and -infinity to JDK11 drop next year. I'll try to catch up > with the conversation during till next week - the stated position needs > more elaborate explanation, but I don't want to repeat others (too > much). Thanks. Fair enough. It would be good to link the -1's (or -0.5 to -infinity :-) ) to alternative answers to the problems we face though. On JDK 8, how would you envisage solving eg. the Maven indexer issues, or other (currently) non-optional dependencies and modules needing access to JDK 11+ APIs? Who is going to do the extra work that will lead to? On not dropping JDK 11 next year, what supported matrix of JDKs do you think we should aim for with the platform and the IDE? Do you think we should support and test across 4+ concurrent JDK's - JDK 11, 17 and 21 LTS as well as current? Where are the resources, CI, manpower and release testing for that? Do you support an LTS-2 strategy, dropping JDK 11 when JDK 25 is out? Or is the JDK LTS status irrelevant in choosing our support matrix, and if so what should that be based on? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
