That's not necessarily correct. Lots of games aren't released until they are version 2.something.
You might also argue that 0.7 in this case is, in fact, 0.07.
At the end of the day, the developer determines how to version the development.
My projects (not games) usually reached above 1.5 before they were actually releasable.
Version 1.0 is used as a major milestone, indicating that the software is "complete", that it has all major features, and is considered reliable enough for general release. A good example of this is the
You must be registered to see the links
, which was first released as version 0.01 in 1991,
You must be registered to see the links
and took until 1994 to reach version 1.0.0.
You must be registered to see the links
The developers of the
You must be registered to see the links
emulator
You must be registered to see the links
do not ever intend to release a version 1.0 of the program because there will always be more
You must be registered to see the links
to emulate and thus the project can never be truly completed. Accordingly, version 0.99 was followed by version 0.100.
You must be registered to see the links
-
-- From Wiki, I know but it's pretty accurate
This has been my general understanding of software releases. 1.0 is general release, 2.0 major changes to an engine, etc. The .1, .2 incriments are generally minor changes(Or story continuation in porn games it would seem) and a,b,c etc are bug fixes, they can also be released as 1.1.1 though, as an example as a bug fix for version 1.1
This hasn't stopped people releasing al-sort of release numbers though, I've seen an alpha drop straight into 1.0 before, but this is due to the developers lack of understanding of software release versioning, Alot of amateur developers going against general consensus, but that doesn't make it correct. We just have to guage for ourselves on download a lot of the time.
--
Off topic? Yes.