On 02.02.22 16:34, Neil C Smith wrote:
On Wed, 2 Feb 2022 at 15:07, Michael Bien <[email protected]> wrote:
There was only "latest", the
version scheme change makes that more obvious.
Yes. it was the use of "series" and "point release" ;-)
how can this happen again without a concept of LTS? Can you give an example.
If a plugin maintainer upgrades a plugin and that upgrade causes it to
only work on NB 13+. It should not be installable/upgradable in any EOL
release before NB 13 - even if its in the same catalog.
OK, I get what you mean. I've been assuming we'd want at least an
overlap of previous and current? Do we want an updated plugin catalog
available for daily builds and RCs before release, and I'm not sure
everyone wants to update immediately on release? Do we want plugins
to be verified in any way? Or maybe just hidden on reports that they
stop working?
I mean my example was an extreme case. I don't think this would be the
general case. Its in the interest of the plugin maintainers too to not
break things right away - but if they want or have to for some reason -
i think its fine too. It would only mean that there won't be any updates
to already installed versions of that particular plugin on EOL NB
installations.
The general case would be that It is likely that plugins will remain
compatible for a while even when you don't update NB right after release.
The question here is: how important is the extreme case? Would anyone
actually want to branch their plugin and release updates for NB.eol and
NB.latest in parallel? Because thats when we really should add multiple
catalogs :)
And btw i believe there is still the option of a "custom update center"
for anyone who needs full control over it, right? I think i had that
over a decade ago for the NB GL and CL packs back when java.net was
still around. (maybe the plugin portal 1.0 didn't exist yet?)
Also, just because we EOL doesn't necessarily equate to a release
being EOL everywhere. Whether we want to support plugins for other
distributions is another matter, or whether many still exist anyway.
If there is a distribution which packages NB 13 and doesn't upgrade it
for the next 5 years. There is not a lot we can do about this (unless we
let NB upgrade itself) - some plugins won't be upgradable/installable
after a while.
best regards,
michael
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
---------------------------------------------------------------------
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
