News for hackers. Stuff that matters.
Re:Chronologic Versioning: No more arbitrary version updates... by azinman2 on Thursday January 02, 2020 @02:10AM (#21933543)
“ After all, macOS 2017.09.25 seems far more descriptive than "10.13", which means nothing to anyone.”

I don’t understand this argument. Dates are arbitrary, and are subject to how quickly something is released/iterated on. Was there 2 releases a year? Once every two years? It’s hard to understand between different versions how many major potential changes there are.

For something like macOS, the number of fundamental under the hood changes are tremendous, coming from a super large organization. Without semantic versioning, it is difficult to create dependencies or explain compatibility, let alone understand how “old” a version someone might be on —- time itself is subjective, while an incrementing counter is not.

Re:Chronologic Versioning: No more arbitrary version updates... by baq on Thursday January 02, 2020 @03:35AM (#21933811)
incrementing a counter is as informative as taking the current date. if you want to embed some information about the software in its version number, you have to define the protocol either way, i.e. what events increment a counter.

see also vector clocks.

Re:Chronologic Versioning: No more arbitrary version updates... by strbean on Thursday January 02, 2020 @06:57PM (#21941370)
You should write a spec for vectored versioning and register vecver.org to host it :)
Re:Chronologic Versioning: No more arbitrary version updates... by baq on Friday January 03, 2020 @08:27AM (#21945623)
bzr may have done it already, disregarding the fact that build version != source version.