On 02.02.22 14:55, Neil C Smith wrote:
On Tue, 1 Feb 2022 at 10:54, Michael Bien <[email protected]> wrote:
the plugin portal would need a NB 13 tag soon. Highest version is NB 12.0.
maybe we should remove the .0 from the other tags too?
Well, it's no more or less of a problem than the missing 12.1 -> 12.6! :-)
There have already been plugins that weren't compatible across that
range.
i mean there is only 12.6 in the 12.x series in my book - nobody should
spend time testing something on 12.1 right now for example IMO.
A NB 12 tag would imply 12.6. With NB 13 the point releases are gone anyway.
But looking at the redirect list... its probably better to not touch the
old .0 tags, the list is big enough (even though having 12.0 next to 13
can look confusing).
I don't know the details how the module upgrades work. But having only
one catalog sounds like the simpler solution (i like simple). If a
plugin has the module dependencies properly set, it won't install on old
NB installations, right? It also shouldn't appear as an update
suggestion - hopefully. (if it does we could probably fix this in NB I
suppose)
I think one reason for the new versioning scheme was to show that there
is only one supported version at a time and encourage upgrades. Versions
become meaningless. (example: I don't even know which firefox version i
have installed, but I do know its the latest)
-mbien
---------------------------------------------------------------------
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
