On 23.09.21 14:59, Neil C Smith wrote:
On Thu, 23 Sept 2021 at 13:38, Michael Bien <[email protected]> wrote:
If the plugin portal mechanism works ok
with major.minor, why change it.
Given the current plugin portal mechanism *doesn't* work OK, then it
would be better not to let it sway this discussion - see eg.
https://issues.apache.org/jira/browse/NETBEANS-5064 That we serve the
same catalog to 12.0 and 12.5 is already a problem.
if this case is common it would show that there already isn't a
major-minor distinction and would simplify the decision to move to a
rolling versioning scheme.
But if this is a single incident then this might only indicate that some
breaking php changes should have stayed in a branch a bit longer and
wait for the next major release.
Given there have been incompatible updates between 12.x versions, I
also think that's a really good argument for switching to 13, 14, 15
in fact? Works well for the JDK!
i am fine with it. If there is no meaning in the major version number
already, it is redundant. If we can still come up with a meaning for it
- keep using it.
-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
