On Mon, 11 Jan 2021 at 02:16, Laszlo Kishalmi <[email protected]> wrote: > I'd like to express my thought about that our 13.0 meant to be next LTS > released in May or early June, does not make much sense.
Probably not a surprise, but +1 to this. > I'd propose release a 12.4 instead, maybe a 12.5 in September > (supporting Java 17) and 13.0 in November, maybe LTS with stable Java 17 > support. Agreed that could make sense, *if* we keep an LTS, to make it the *second* release after each Java LTS, and sync those two things up. I know people may make the argument that we're more than a Java IDE, but to me this would also be about the recommended JDK to run with. > Also thinking about dropping LTS as it is. Well, until we know what it is! :-) > And lastly, I'm feeling that having 4 releases in a year is a bit to many... However, I'm definitely -1 to this. That's not without the caveat of thinking there's room for improvement around API review, issue handling, and testing, etc. leading up to freeze dates, and being stricter about what is allowed into the release branch post-freeze. No more "can we squeeze this change in?" :-) I think less frequent releases actually put more pressure on each release, and we'll end up with inevitably longer release cycles but just as much work. If we drop or change LTS as is we might want to rethink what NetCAT is / means too? Maybe as well as a more formal NetCAT with any less frequent LTS, we need to open up and encourage running the various tests against daily builds throughout the year? 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
