Version: (using KDE KDE 3.5.7) Installed from: 00 According to http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule RC2 will be tagged on 2007-12-05 while the final 4.0.0 release will happen on -12-11. There are no dates for RC2 release and final 4.0.0 tagging. I guess there will be no RC2, but having no evidence, I'm letting someone else fix it.
RC 2 will be the final release if nothing goes wrong. That's the notion of a "release candidate". I clarified the text a bit.
Cornelius, I see, I didn't expect that, but nevertheless there's no release date for RC 2.
Reopening due to lack of RC2 release date.
The schedule clearly states that RC 2 is released as final 4.0.
Cornelius, I hadn't understood that RC 2 wouldn't be released (unless it becomes KDE 4). I clarified the page considering that - hoping I didn't misunderstand.
RC 2 will be released, either as RC 2 with an RC 3 scheduled after that or as final. I updated the page to accurately reflect that.
I see - IIUC RC 2 will only be released as RC 2 if it is buggy. That's a bit counter-intuitive, but I think I understand; I'll clarify the page unless I'm missing something.
While I was going to proceed, I figured out what the real plan is (hopefully this time!). To avoid you being as confused as I was, one important clarification: while you're right that release candidates can be final, a release candidate can't be released both as a RC and a final at the same moment. For example, the following plan is possible with the usual and language-abusive meaning of "release candidate": alpha beta tag RC1 release RC1 tag RC2 release RC2 tag .0 release .0 Or, unusual but respecting the meaning of "release candidate": alpha beta tag RC1 release RC1 unless RC1 is found to be buggy, re-release RC1 as .0 KDE 4's schedule is in the first case, so I scrapped the RC 2. Hope it's clear now :)