3 ms·
The funny thing about trunkver being "compatible" with semver is that it is not semantically compatible, only format compatible. You could (but not necessarily
by rswail 2y ago
The funny thing about trunkver being "compatible" with semver is that it is not semantically compatible, only format compatible.
You could (but not necessarily should) combine them by making the trunkver the "patch" part of semver.
In our work, the semver is kept separate from the build version. We use a build versioning of vYYYY-MM-DD[.hhh] where hhh is for a "hotfix" of a previously released version.
The version of the "next" release can be set (either in advance, or based on a sprint or just the current date).
- nickez 2y agoIt would be semver compatible if they used 0.DATE.0 or 0.0.DATE instead. from semver spec: 4) Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.