How about new RC?

[rsmithgs]

Maybe the versions given to releases initally were wrong, maybe RC1 should have been Beta one and the fact there are 3 RC2 versions maybe they should have been beta 2-4. But cannot change the past and re-versioning the releases now would cause confusion.

But as I see it this doesn't mean that RC3 should be released with missing features and known bugs.

On the other hand without a stable or even milestone release there is no testing in anything but testing environments. (That is generally speaking, I know there are those that are running RC's and the trunks as production servers, hell I even have a semi production box with a trunk on).

Is there some middle ground that could be agreed upon? Maybe a RC2D release with only the outstanding security issues fixed? The reason I propose this is the following:

1. Almost everyone wants the RC3 release to have the major bugs fixed and not released before then.

2. RC3 could be quite a way off from been launched due to Rats commitments.

3. Those that are running the last RC would have a version to upgrade to that would allow some production testing on the added features. (I'm guessing but I'm sure someone would be more willing to write a full upgrade document/script to upgrade between RC2C and RC2D then from RC2C to whatever the latest trunk is).

4. Would give a stepping stone between RC2C and RC3 which seem vastly different, may also be easy from an upgrade perspective. Rather then users upgrading directly from RC2C to RC3 they would upgrade to RC2D first.

5. May take most of the pressure away from launching the next release.

Please don't think I'm whining or trying to force change etc. Its merely a suggestion which would hopefully benefit everyone and the project as a whole