Fixing bugs, and a synopsis of our versioning policy

Continuing work on v4, I'm fixing up bugs reported by the QA team, and found in my own testing. I have fixed several so far, and more to come. A new build will be released later today. I must say that I am not happy with the state of RC1. I mean, its alright -- but just not all 'clicking' yet (to sum it up). The new release will be v4.00.02 RC1 (yes, still RC1.. I have my own versioning system ;p).

Here is how my versioning works, so you know where we're at:

• BETA = not all features implemented or likelihood of bugs exist
• RC1 = All features implemented and no more to be added (feature freeze). Generally works, but not bug free.
• RC2 = Better tested, bugs squashed
• RC3 = Performance tested, ensured to be as good or better than last final
• FINAL = Fully tested and ready for general use

Yes, it could be said I'm not using RC1 as literally as they should be. After all, it should be a true Release Candidate. Maybe, but again I'll let Microsoft set the example. Their RCs are about like the above system.