New versioning scheme of major.minor.patch
Well, basically we almost have such a numbering scheme. The old "official" release was 1.0 RC2, so there is major.minor RC-SUFFIX. You could also say we had a patch level once as in 1.0 RC1-1. The problem is not the numbering scheme, the problem is that we have moved to RC too early once, which we cannot take back.
Actually, I think the RC3 terminology is what is confusing everything,
The problems with revision numbers and releases are well-known to us. We have discussed what to do to get out of the Dead Marshes alive many times, and we agreed that following our guide, whilst knowing he will lead us to evil, is the lesser risk.
Some things really did not work right in RC2, and RC2 was quite unusable in many respects. We still have a non-working code completion today.
From this point of view, one could argue that technically, we
are going through RC stage because we fix things that don't work. However, it is quite obvious that this is not true
Yes, we have been adding many features and we still are. This should not happen at RC stage, and we know it. The correct thing would probably have been to call the next upcoming release alpha-6 or alpha-7.
However, the evil that comes with changing the version numbering is still greater than the evil of going on as before (or so we believe). We would not want to confuse the users yet more by jumping forward and backward in time with our releases.
2. Intermittent alpha releases
I am against intermittent alpha releases (and so was Mandraman when we last talked about this) because it will probably lead to even more confusion and yet more problems.
@BigAngryDog: Hey, you wear the same kind of stupid-looking hats as I do! Very cool