I really prefer the Bitwarden approach to versioning, by including the date like YYYY.MM.DD.whatever. Makes it easy to know how old a version is at a glance, and easier to remember.
I prefer the SemVer Major.Minor.Patch approach so I can tell at a glance if the update breaks compatibility or is just bug fixes. Technically the Patch part can be any number as long as it increases each update of that same Minor version, so one could write the versions as AA.BB.YYMMXX where AA is the Major version, BB is the Minor, YY is the two digit year, MM is the month, and XX is just an incrementing number.
I think this approach has the best of both systems.
I really prefer the Bitwarden approach to versioning, by including the date like
YYYY.MM.DD.whatever. Makes it easy to know how old a version is at a glance, and easier to remember.I prefer the SemVer
Major.Minor.Patchapproach so I can tell at a glance if the update breaks compatibility or is just bug fixes. Technically thePatchpart can be any number as long as it increases each update of that sameMinorversion, so one could write the versions asAA.BB.YYMMXXwhereAAis theMajorversion,BBis theMinor,YYis the two digit year,MMis the month, andXXis just an incrementing number.I think this approach has the best of both systems.