On 02.02.22 15:54, Neil C Smith wrote:
On Wed, 2 Feb 2022 at 14:42, Michael Bien <[email protected]> wrote:
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.
...
I think one reason for the new versioning scheme was to show that there
is only one supported version at a time.
There never was a 12.x series! There were no "point releases". There
is zero difference between upgrading 12.5 -> 12.6 as between 12.6 ->
13. The only thing the "major" increment differentiated was new LTS,
which we no longer have anyway.
The main reason I proposed the version scheme change is that still
no-one understood it! :-)
yes exactly. There was no LTS anyway. There was only "latest", the
version scheme change makes that more obvious.
I don't know the details how the module upgrades work. But having only
one catalog sounds like the simpler solution (i like simple).
Simple is per-release. See what happened for PHP plugins here between
12.2 and 12.3 -
https://lists.apache.org/thread/bnk1dg8dcnq1bslq2dvs1grv5hvzgdtm That
problem will reoccur.
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.
-mbien
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
