Just wondering what the Numbering logic for ]project-open[ packages is.
It isnt Semantic Versioning (https://semver.org/) and I realized I never bothered wondering about the logic of the 5.0.3.0.1 versioning.
Would my assumption be correct, that we actually do have Semantic Versioning, where 5 = Major Version, 0 = minor version and 3 = patch, whereas the 0.1 (and so on) allows us developers to differentiate versions?
This way we could have our own (versions of) packages, but always state through the 5.0.3.x.y which ]project-open[ Version it is meant for?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just wondering what the Numbering logic for ]project-open[ packages is.
It isnt Semantic Versioning (https://semver.org/) and I realized I never bothered wondering about the logic of the 5.0.3.0.1 versioning.
Would my assumption be correct, that we actually do have Semantic Versioning, where 5 = Major Version, 0 = minor version and 3 = patch, whereas the 0.1 (and so on) allows us developers to differentiate versions?
This way we could have our own (versions of) packages, but always state through the 5.0.3.x.y which ]project-open[ Version it is meant for?
Hi!
I'd prefer that you mark forked packages by something like intranet-core-cognovis or similar...
Cheers
Frank