On Tue, 23 May 2023 at 20:20, Matthias Bläsing <[email protected]> wrote: > testing the voting candidate, I noticed, that the JS scanning can run > into a ConcurrentModificationException. ... > For me this is not a big problem as described above, but people using > plain JS in the IDE might face bigger problems. At least the message > log gets flooded and of of course you'll get annoying exception > bubbles. > > Sorry about that.
That's fine! It happens. But this is a discussion thread, so what exactly are we discussing? How do you think we should proceed? I guess there are at least 3 choices - 1. Pull the vote. Doing that means throwing away about 8-10 hours of work across 4 people, and will delay the release by a couple of weeks. 2. Do an 18-u1 release in a couple of weeks to push this fix, and any others that arise, via the update centres. Do we have a volunteer to RM? I'll help if need be, but won't be able to put much time into it. 3. Proceed as is, and provide information on how to mitigate the issue. I'm also concerned why this hasn't been picked up during the release candidate phase? Those are cheap to produce, voting candidates are not. In particular now we've moved to a consolidated vote. Are there things we could improve in our RC testing? Voting candidates should not need to be tested for functionality. Thanks and 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
