On Wed, 13 Jul 2022 at 18:17, Matthias Bläsing <mblaes...@doppel-helix.eu> wrote: > from my perspective all "Verification" can do is to check a plugin > looks normal and does not immediately destroys your data. Everything > else will not scale (and yes not doing verification at all is IMHO an > option). > > What we could do is this: > > - tie verification to a plugin version not the NB-Version<->Plugin > Version combo
+1. In effect we've been doing this with the wrong plugin centre anyway! The key thing I guess is the ability to unverify - ie. pull a plugin from a version catalog if there are reports of issues with installation, etc. > I added Jiří Kovalský as a direct To, so that he is aware that this > discusssion is happening. Thanks. I was going to do similar too shortly. However, ideally [PLUGINS] tag is all that should be needed. > I'm willing to make code changes to the plugin portal, but I don't want > to be rushed, so I definitely won't release any code for the portal > this week. Not expected. I'm not trying to rush anyone into making any changes in the next week. Just a decision on what we're going to do so that we can set up necessary things for the release candidates. We need a process that we know can be delivered and be sustainable by release time for 15. The status quo does not appear to be that, as we're still not ready for 14 yet. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
