Actually, it depends. There isn't much of a pattern for versioning. Some devs would follow 0.9 with 1.0, but that doesn't mean it is the end of the alpha or beta phase Just like some devs use 0.9a/b/c for minor updates and others use 0.9.1/2/3 just the same.

I like to use the format x.y.z in which x would be major updates which add new features or indicate an important milestone (like end of alpha/beta), y for updates of existing features or new content and z for minor updates, meaning bugfixes, refactoring, minor optimization or some other kind of smaller changes; Depending on the scale, i'd consider it a "y".

But like i said, there isn't really an standard pattern to use, and like you said, the version usually doesn't indicate how close it is to being finished.