On Sat, 22 Oct 2022 at 13:13, Michael Bien <[email protected]> wrote: > On 21.10.22 14:24, Neil C Smith wrote: > > On Fri, 21 Oct 2022 at 12:43, Michael Bien <[email protected]> wrote: > >> well, this was my first suggestion but it met resistance :) > > I know. I agree with you. My issue with the resistance, and some > > points are definitely valid, is that it's based on a somewhat false > > idea of what we've been doing for the last few years of releases. > > > >> I would just leave everything verified. The community could filter > >> problematic plugins out which are not updated. > > We can't leave verified as far as I understand. We would need to bulk > > verify everything, unless we go back to a shared catalog. And if we > > go back to shared catalogs, we can't filter by release. > > well, this somehow doesn't sound like a showstopper to me. Something > could just add that flag in some automated fashion, no?
You would hope so! We have yet another user thread or discussion expressing frustration about this at https://github.com/apache/netbeans/discussions/4849 I totally agree with the points raised there. We haven't had a vaguely useful plugin catalog since NetBeans 13. The plugin catalog for 16 is currently empty, so we're missing possibilities for testing. IMO an empty plugin catalog is a reason to delay the release of NetBeans 16 until it's ready. 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
