Wow, I remember this. Every rebirth of this has less and less though.
Should be version 0.0.7 really. 0.7 makes it look like almost half done assuming 1.0 is first release.
That would be the case if version numbers were decimal not just arbitrary numbers, 0.7 does not mean 70% complete it just means seventh (pre/alpha/beta)release, much like 0.9999 would just be the nine thousand, nine hundred and ninety ninth release, all a 1.0 means is that its shippable/complete and what bugs exist "shouldnt" be fatal to play.
For the record i wish everyone used semantic versioning as its the easiest way to do disciplined releases (and from a dev point of view the easiest to manage bug reports against a specific version) thats the typical 3 - 4 digit version numbers you see. which reads as
version.
major-revision.
minor-revision.
optional-build-number
Where Version = the version of the code base, although in this community you would rarely get a 2.0 release unless you count a rewrite in a different engine, so here a 0 would read as under development, and a 1 would read as complete
major-revision = new feature(s), levels, characters, plots
minor-revision = bug fixes, spelling and gramer corrections, to something added in the last major revision
optional-build-number = only really used as a way of keeping track of and testing minor revisions
Unfortunately will never happen, its hard enough to find pro dev teams with the dicipline to do it correctly in commercial software, nevermind in what is typically side projects and passion projects done in spare time like 99% of the games here...
Apologies for the tangent just versioning misconceptions are a pet peeve of mine,