On Wed, 15 Jun 2022 at 03:07, Ernie Rael <[email protected]> wrote: > Might be good to add a version button for a new release early in the > process, maybe during RC.
+1 (again) - from a releases perspective. In fact, possibly from point of previous release, as we need to point the plugin centre URL for dev builds at something, and testing earlier might make sense. > I'd guess it's very rare that a plugin stops working. If an automatic > extension to the next release, or something like that, isn't acceptable, +1 (again) - I think we should work on a remove on report basis after initial verification. We effectively had automatic extension from 12.0 to 12.6, because we used the same plugins URL. A couple of plugins broke in that time too. There is no greater change from 12.3 to 12.4 than there is from 13 to 14! So, why not *stay* with automatic extension? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
