4 ms·
Because version numbers are an implicit signal of maturity. The convention is that a 1.0 software release is complete. It's understood that it's not the final r
by scott_s 18y ago
Because version numbers are an implicit signal of maturity. The convention is that a 1.0 software release is complete. It's understood that it's not the final release, and it may still contain bugs, but it's a common signal to indicate "This is the first version of my software I feel is complete enough that I'm comfortable releasing in the wild."
Some applications have their own numbering conventions to indicate what kind of an update a new version is. If you're familiar with the software, it's useful to know at a glance what to expect. (The Linux kernel and gcc do this.)
You can ignore this convention, but you're going to encounter confusion from potential users.
- nostrademons 18y agoYet there's crazyness like Sun renaming Java 1.5 to Java 5, or Python 3 to Python 3000, or Netscape 4.7 to Netscape 6.0. Many of these are explicitly for marketing purposes, because a competitor had a higher version number. It's moronic to compare version numbers across products precisely because standards vary so widely. I'd say that Django 0.97 was more stable than Rails 2.0, yet it's not even a 1.0!