Hi Matthias,
although I am not very involved with the plugin portal, the changes do
sound like good improvements to me.
The first solved issue I did notice myself once and thought at first
that I did something wrong while requesting verification.
The second improvement should greatly reduce verifier workload due to
re-verification requests after NB updates, while still retaining some
interaction with the maintainers - sounds good too!
(Although this probably requires that the notification mails are sent in
time too)
speaking of which - would be good if some of the verifiers could also
participate in this discussion ;)
thanks for working on this,
michael
On 24.11.24 19:55, Matthias Bläsing wrote:
Hi all,
as the verification process of plugins was once again raised multiple
times in this NetBeans release timeframe, I implemented two
enhancements, that I think represent the current discussion state and
have the intention to reduce review workload.
Please have a look at:
https://github.com/apache/netbeans-tools/pull/72
Text from PR copied here:
==================================================================
There were two separate concerns raised regarding the current
verification process. These are the two relevant use-cases:
Release a new plugin version
--------------------------------
The steps that are needed to release a new version of a plugin and get
it into the plugin portal are:
1. Author release the plugin to maven central
2. For all NetBeans versions that the new version of the plugin shall
be available, the author has to drop the verification for the current
version of the plugin.
3. The author requests the verification of the new version of the
plugin for all target NB versions.
4. 1. Verifier verifies the plugin
5. 2. Verifier verifies the plugin
The problem is, that between steps 2 and 5 the plugin will not be
available in the IDE for installation. Neither the "current" version,
nor the "new" version.
To fix this 9ff6052a10e7c30e0c7ec881580c1c7f5eaae542 changes the work
flow slightly to:
1. Author Release the plugin to maven central
2. The author requests the verification of the new version of the
plugin for all target NB versions.
3. 1. Verifier verifies the plugin
4. 2. Verifier verifies the plugin
The Portal only blocks "Request verification" if either the current NB-
Version/Plugin-Version is already verified or there is another
verification for this Plugin/NB-Version is already pending. The
"current" version stays verified until step 4 is executed, then the new
version becomes the "verified" version and the verification for the
previous version is automatically dropped.
This way there is no "dead" timeframe where no plugin version is
available for installation.
Release a new NetBeans version
-----------------------------------
For each plugin the author has to decide for which NB versions which
Plugin version should be available. So after a NetBeans release each
actively maintained plugin needs to get a new NB-Version/Plugin-Version
verified.
This can lead to delays until all plugins are available for
installation on an updated NetBeans version.
0e90bd830d5495b6224cc07dfd9b55ec6c087ad7 proposes to change this to a
mode. The idea is, that authors can "Request validation" for a new
NetBeans version and that request is immediately granted if that plugin
version is already verified for at least one NetBeans version. The
idea:
- the author is responsible for the general usability of the plugin
- verifiers check that the plugin basicly does what is promised and
behaves in a sane way and does no harm.
The latter should not be affected by NetBeans updates and even if so,
would be in the interest of the author not to expose that version to
the new NetBeans version.
==================================================================
I'd appretiate feedback
Matthias
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
