I am still using "linux versioning" for some projects and personally prefer it over date based versioning.

you simply increment numbers till you feel they are high enough, then you bump the major version.

"X.0" has no particular meaning - its a version like any other.

I think this would work well here too since tooling like launchers don't really need versions for marketing purposes.

-mbien

On 22.12.22 07:17, Arnaud bourree wrote:
Hi,

Without any binding, I prefere semantic version like 1.0.
I know that nowdays major version change is most of the time marketing
change.
With yyyy.mm version you will ask why the last version is so old : because
nothing new to add ...

Arnaud

Le mer. 14 déc. 2022, 18:15, Eric Barboni <[email protected]> a écrit :

Hi,

https://github.com/apache/netbeans-native-launchers or
https://github.com/apache/netbeans-native-installers are using version
taken
from Apache NetBeans main repo.

But their resepective lifecycle are not in synchro with NetBeans. They
should be voted and incorporated before main vote. It will always be tricky
to get proper version.



On a PR we proposed to change to YYYY.MM format for this external so we
could have an easy way to know when it was release.



Any better ideas ?



Best Regards

Eric




---------------------------------------------------------------------
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



Reply via email to