OK, you may call us "lazy" because we haven't released an official version (be it 1.0 RC3 or 1.0 final or anything like that), but we have our reasons for not doing so, and BTW, we don't have an obligation to do it.
We could just take the current revision, tag it RC3, create the installer and release it, but I don't really think that would be a wise move. If you check the nightly builds forum you will find that every nightly fixes a few bugs, improves here and there, but also, sometimes, some new and serious bugs are introduced.
Right now we're trying to fix as many bugs as possible and also trying not to add new features (except if they're trivial ones). We are aware of the importance of a stable, or "almost stable" (as in Release Candidate), version, but... should we release it just because?
You don't have an obligation to constantly download nightly builds, in fact many of us use a single revision for quite a long time before updating to the most recent one.
What you can really blame us for is trying to get a 1.0 version very quickly and just after releasing RC2 doing such a lot of changes. I think we all agree all those changes were great, but perhaps we should have tried to stabilize what we had, create a branch, release a 1.0 final and what we're working on right now call it a 2.0 alpha/beta or something, but it's too late now.
So, don't be in such a hurry, RC3 is coming, but it will be released only when it be ready, and we all hope it will be soon.
