On 24/11/18 4:43 AM, Geertjan Wielenga wrote:
Simplest solution is for more to join in with the verification process.
It’s not much work and anyone is welcome to join in.
Maybe even simpler is simplifying the verification process. OTOH,
changing process may never be considered simple 😉
On 24/11/18 4:51 AM, Jiří Kovalský wrote:
I agree. We certainly need more plugin verifiers. Right now it's just
4 volunteers, which are obviously overloaded, as there are 1.5 month
old plugin verification requests still waiting in the approval queue.
Or you can create a voting on relaxing the verification process.
I vaguely recall a question (unanswered I think) about whether the
plugin portal was "owned" by NB and so whether or not how it operates
could be voted on.
There's been plenty of discussion about relaxing/adjusting the plugin
process. There's a thorough discussion starting from October 19, 2022
[PLUGINS][RELEASES] Preparation for NetBeans 16 plugins
https://lists.apache.org/thread/yb3smkz109ownxlk81t61gvgzl6479j3
And similar threads in the years after that.
AFAICT, there's at least 3 types of plugin to consider
1. Existing plugin, no changes since previous release.
2. New version of an existing plugin.
3. New plugin.
There's been general agreement in most comments that for (1)
automatically verify for the next release. I wonder how many of each
type are in the queue. I don't recall if there was general agreement on
the handling of (2) and (3); here's some hand waving for them. For (2),
an updated plugin, where there's a "history" a history of previous
versions, could be automatically verified. For (3), a new plugin should
have the strictest scrutiny before verification (is that like how it's
done now?).
IMHO, a key/critical part of this is having a way for user feedback to
revoke verification. Issues? Plugin category of discussions? Keep in
mind that discovered problems could be with the new version of NB and
not the plugin.
-ernie
