I'm physically training a lot :D Will be fit on 12.0 release :p Feature freeze is a bit abstract to me. After merge close, all of us should be careful of PR that will go for 12.1 or 12.0 LTS.
In some way I feel that RM on early phase can be more group work (it was a bit like that in 11.3) : making a branch, setting up json and pushing build button on Jenkins for beta creation can be done by any PMC. (No signing, no vote ..) and making changes remerging for beta milestone is quite easy too, with help of PR. That lower the workload. The remaining works is locked to RM but it's a matter of hours for each round of candidate. The hard stuff is VC preparation with signing that is done by RM and co RM (for installers) on their own computer. -- What I'm start thinking is instead of a xx.u-update1 it will be quite easy to go for xx. instead of complex construct (if 11.3 need patch then go to 11.31) full updating web + mirror with the 11.31. This is informal :D Best Regard Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : mercredi 11 mars 2020 11:08 À : dev <[email protected]> Objet : Re: Apache NetBeans 12.0 -- Eric Barboni On Tue, 10 Mar 2020 at 12:22, Geertjan Wielenga <[email protected]> wrote: > Especially Eric, who volunteered to be volunteer release manager for 12.0. I'm glad Eric is doing 12.0 - I think having someone who has already been an RM is a good thing to keep in mind for future LTS. I'm also happy to pick up any tasks here if need be, and it might also be good if the person considering doing 12.1 touched base now too? Am aware that this release process will be twice as long, and have NetCAT, as well as potentially more likelihood of updates through the year - all potentially increasing the RM workload. Eric, any thoughts there? On updates, part of me feels we might want to find "something" that needs updating in 11.3 and test changes in pushing updates across larger user base? On Tue, 10 Mar 2020 at 13:12, Geertjan Wielenga <[email protected]> wrote: > — Make nb-javac less prominently required and explicitly state that > ideally a JDK later than 8 should be used. Possibly an option to switch off the notification (similarly to the old userdir one) would be good? 12.0 may not be the time to be too radical in changing that process, but being able to stop it nagging and more info in the download dialog would be good. > — Several small but annoying bugs in the FlatLaf support (see recent > e-mail here by Jaroslav Tulach). Well, on the FlatLaF / HTML wizards front, I'd much rather see us drop the HTML wizard entirely! Assuming we don't, we really need to battle test the ergonomics enablement and JavaFX download there. It too often results in an infinite enablement loop and blank wizard. > — JDK 15 enhancements being worked on by Oracle developers, e.g., new > sealed type etc. Do those really need priority in 12.0 vs 12.1? Freeze is in a week! More importantly would be ensuring JDK 14 support, including nb-javac when installed? 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 --------------------------------------------------------------------- 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
