Hasn't Ubuntu done year.version for a long time?
What's the "best" way to version your product?
11–16 of 16 posts
Re: What's the "best" way to version your product?
#12I developed and shipped one product with monthly releases for decades and always simply bumped the version by one: 1, 2, 3.. Anything fancier doesn't really tell you exactly what features changed when, so a table in the documentation spelled that out for each version.
Re: What's the "best" way to version your product?
#13I like the classic as it provides actionable information. Although knowing the date is nice, especially to indicate an application is dead end. But I rarely need that. When I first download it, and when I wonder ... hmm is this product ever going to be updated. I am not sure what the value of putting the year in the version. For my own home projects, and work pre-release, I always list the build date on the screen. S…
I suppose it is finding the "perfect balance" for human reading and customer support.
Re: What's the "best" way to version your product?
#14On the other hand, unlike products, libraries still make sense to version semantically as it is technical information for the users of those libraries that clearly communicates breaking changes.
Re: What's the "best" way to version your product?
#15Re: What's the "best" way to version your product?
#16Who’s your user base?