On 22.09.21 19:01, Ernie Rael wrote:
On 9/21/2021 10:50 AM, Geertjan Wielenga wrote:
2. *The next major release.* [snip] From 13
onwards, maybe each release should be a major release, i.e., there are
enough numbers in the world, we don't need minor releases anymore after
that breakpoint.
This essentially makes release numbers meaningless, which seems to be
the way things are going...
i think this versioning scheme makes the most sense for rolling software
releases. If someone would ask me which firefox version i am using, i
wouldn't know without having to check. The only right answer is: latest
- why bother with the details. But if someone asks me what linux kernel
i am using I could reply 5.10.x. Since the fact that it is the 5.10
branch could actually matter.
In the old days major version numbers were mostly only incremented when
there was a good reason for it. For NetBeans, such good reason could be
the migration to the next java LTS release. NB 13 could have a JDK 11
code base, NB 14 a JDK 17 code base. Everything else would be update
releases (unless there are other good reasons to bump the major release
number, larger changes, like the before mentioned nb-javac, etc).
since it ultimately doesn't matter I would suggest to keep the least
disruptive versioning scheme. If the plugin portal mechanism works ok
with major.minor, why change it. Keep releasing 12.x until there is a
good reason for 13.0.
regards,
michael
---------------------------------------------------------------------
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
