On Wed, 27 Nov 2024, 20:55 Matthias Bläsing,
<mblaes...@doppel-helix.eu.invalid> wrote:

> Because "Request validation" is an action the author can decide to do
> or not do. "don't validate" is not. It would be an invisible side
> effect of creating a new NB version in the portal.
>
> If the author can't be bother to test the plugin, it is not fit to be
> shipped. And if you want it regardless, you can use the catalog für the
> previous NB version.
>

As I've said before, I disagree with this. For seven releases 12.0 to 12.6
we did not require this, nor could we. Switching to a single incrementing
version every release was not intended to cause this extra overhead for
plugin authors, and all it achieves is less testing of the APIs during
releases. A plugin not functioning is just as, if not more, likely to be an
issue on our side!

Best wishes,

Neil

Reply via email to