On Fri, 25 Oct 2019 at 07:48, Geertjan Wielenga <[email protected]> wrote: > we need to do whatever we can to make the following PR for the new > nb-javac available, or else refactoring will be broken for everyone with > nb-javac installed in 11.2:
Yes, it's a shame we're releasing knowing that we need to ship an update. I'll start moving release artefacts on to dist now, but will leave removal of NB 11.1 for a few days until everything else is ready. If anyone can input on how we get our processes for shipping updates in better shape then please participate in that separate discussion thread - it's probably our most urgent problem to solve right now! There are some lessons to consider here about our release schedule and how strict we are about freezing. The updated nb-javac was added after freeze, and has also been a cause of a few delays - it was not until beta3 that it was even testable. However, without it we'd be missing Java 13 support. Whether we need to make sure these changes land before freeze, or push our schedules back a few weeks around JDK releases might be something to consider. A particular concern might be how much we can ensure JDK 14 is considered in NetCAT for NB 12.0. 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
