On Thu, 20 Oct 2022, 17:46 Matthias Bläsing, <mblaes...@doppel-helix.eu.invalid> wrote:
> Hi, > > Am Donnerstag, dem 20.10.2022 um 18:35 +0200 schrieb Michael Bien: > > what if we leave the process as is for now but keep plugins in the > > catalog if there were verified within the last 2-3 releases. > > > > This would also fix the problem of having an empty catalog on every new > > release. > > > > I think this might improve the situation until there is a better > solution. > > and will break, if the plugin has a hard dependency on the target > NetBeans version. We recently had a discussion here about access to > flatlaf internals, which is required to get additional flatlaf modules > working. There is a high probability, that this will requirere updates > on every NetBeans version. > Yes, this is true. But we had this problem multiple times in the past and couldn't fix it because we served older catalogs to multiple versions. NB14 was always served the catalog from NB13 because its own catalog was never ready. So I'm in favour of automatically verifying at rc1 stage and using the release candidate phase to unverify broken plugins. Yes, we've had this discussion before. But the promise that we could keep up with release cycles is simply not being met. Best wishes, Neil
