It goes so far, but then falls short – hey, even Apple are guilty of confusing version numbers, ‘Apple releases second iTunes 12.6.1 update with new build number’.
The beauty of using version numbers is that once learned they’re easy to understand*. Something like SemVer wouldn’t cause any confusion or require anyone to look up any arbitrary web page to compare batch numbers.
Strictly speaking SemVer is intended for libraries and dependencies, and as Ryan says, there would be near rioting if this happened with, for example, Ruby.
But maybe using years would be better?
As another point of interest, Docker moved to yy.mm numbering, so we’re now at 17.09. The thing with that is they’re releasing on a fixed schedule.
To round this out, I’ll mention a popular Mac application called Espresso. The developer switched to a X+1 version number where no matter how trivial a change the version number would be incremented. But then after some vocal opposition ‘Updates and licenses are going back to the traditional model.’
* Of course there’s a number of other things to learn, like how versions numbers aren’t decimal and 10.4.9 can be followed by 10.4.10. Of course that number ‘10’ is pure marketing.