The code that the RC builds are made with and the that the CVS builds are made with is NOT the same. The RC builds are coming from a stable code branch, the CVS builds are from the unstable code branch. All bug fixing effort is focused on the stable branch right now so you aren't likely to get any help with problems you have on normal CVS builds until after 3.6.9 is officially released. Use standard CVS at your own risk.
Yep. There are
only a few good reasons to use a CVS at the moment.
1) You're developing a campaign which needs an Inferno build.
2) You're developing a campaign which uses the enhanced Team Loadout options (I can dream that someone is using it surely!
)
3) You're developing a campaign which uses WMCs new limbo code
4) You've had a problem with Taylor's light test build and you want to see if the same problem exists in CVS so the coders have more info to resolve it
That's pretty much it. I wouldn't use CVS for anything else. I certainly wouldn't use it as the standard build I use when playing FS2.
There was no 3.6.8, we skipped it. For 3.6.7 I think that there were about 7 or 8 test builds before release. We were just a lot less organized about it then than we are now.
And we paid the price as a result. 3.6.7 was current for about all of a month and then we were telling everyone to upgrade to CVS builds to solve problems with dual core CPUs and then a whole host of other problems. The idea is to not have that happen this time. 3.6.9 should be stable when you get it. we may end up having to release a 3.6.9.1 build if we find a major flaw but you should never have to download a CVS build to solve a problem (except possibly as a temporary fix).
The only people who should be using CVS from now on are mod devlopers and bug testers. You should never see someone with one or two posts being told to get a CVS build again with luck.
And there will be at least one more RC build for 3.6.9, when we're ready to release it. 3.6.9 official will also be released when it's ready. There is still a lot of work going on behind the scenes.
Yep. It's not as if we're sitting on our hands. Taking a quick look at the commit logs I see about 20 different commits for the last week alone. That means at least 20 different bug fixes and improvements. We don't want to delay the release of 3.6.9 any more than we have to but the quality of the code is improving with every day we make you wait so the end result will be worth it
