https://github.com/tunnckocore/strong-predictable-software-versioning
Strong, easy and predictable, date-based software versioning. Similar to @semver
https://github.com/tunnckocore/strong-predictable-software-versioning
release-management semantic-versioning semver software software-development versioning versioning-semantics versioning-workflow
Last synced: 5 months ago
JSON representation
Strong, easy and predictable, date-based software versioning. Similar to @semver
- Host: GitHub
- URL: https://github.com/tunnckocore/strong-predictable-software-versioning
- Owner: tunnckoCore
- Created: 2019-09-10T06:14:50.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-09-10T10:03:03.000Z (almost 7 years ago)
- Last Synced: 2025-10-19T04:37:50.121Z (8 months ago)
- Topics: release-management, semantic-versioning, semver, software, software-development, versioning, versioning-semantics, versioning-workflow
- Homepage: https://twitter.com/tunnckoCore/status/1171281874368552960
- Size: 1.95 KB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Strong Predictable Software Versioning (DRAFT)
Strong, easy and predictable, date-based software versioning. Similar to SemVer.
Just like SemVer's signature is `major.minor.patch`, here it is based on the ISO-8601 date format `YYYY.MM.DD`, except that we don't put the day, so the signature is `year.month.patch`. This allows us to more freely whatever changes we want through the `patch`. Of course not breaking changes, and primarly bug and security fixes, dependency updates, docs, chore and etc.
This software versioning doesn't mess with SemVer and doesn't breaking it, nor the normal SemVer workflow and tooling. It's just a different perspective of versioning allowing few very unique and otherwise hard to implement or predict things/features.