Strongly agree with your strong disagreement. The blog author doesn't seem to have any experience releasing software that others need to actually rely on. This

Strongly agree with your strong disagreement. The blog author doesn't seem to have any experience releasing software that others need to actually rely on. This dovetails nicely with the discussion yesterday on using dependencies (https://news.ycombinator.com/item?id=31692606 https://news.ycombinator.com/item?id=31692606). I would not want to have to depend on any library this blog author releases. From that list of random meanigless dates, how would tools know which release is a compatible bugfix and which ones carries breaking changes? The assumption there seems to be that release date is the one and only thing consumers of the release care about. But as a consumer of some library, I can tell that I mostly don't care at all about the release date. But I must know what the release contains in terms of change disruption, which is the purpose of versioning.