I suggest we get community consensus on the following points (for as much as that can be done):
- List the features / bug fixes that would make an FC release worthy of the tag 'v1.0' . NormandC's list looks like a good place to start.
- Prioritize the list. Whether it's determined by how important the feature is, or how close it is to being done - whatever.
- Build a development roadmap around that list, establishing certain features be complete before certain versions may be released.
So, for example, if we break NormandC's list into five key categories, we can then identify five 'major' releases between now and version 1.0 and associate very specific features which must be met in order to make the release.
Of course, nothing is set in stone, but it gives us goals and makes it clear what's really important to the project, so we spend our time working on things that really move FC forward for the sake of the community that depends upon it.
I really don't care what versioning scheme we use, and I know we can't predict the future or make guarantees ("it's done when it's done," after all), but if we really want to make version 1.0 a reality, we need to be more intentional about our development roadmap.
Incidentally, the current roadmap in the wiki leaves a lot to be desired... A critical path to v1.0 would make it a much more useful (and maintainable) document.