It's been mere 2 months since 3.7 came out but we've all moved at a break neck pace in that time, and already find ourselves poised for the next.
As I'd mentioned in the progress update, we intentionally set a very aggressive timeline on 3.8 to try and keep focus, and get a feel for how much can be pushed through when that focus takes hold - and also because there were some fairly large issues in the 3.7 release we had not properly caught and tested.
This set the theme for our work on 3.8: cleanup and stability. Linux was a major factor of this: due to oddities with drivers, and minimal testing ability, some pretty big issues slipped past us for 3.7, and while that's never a good thing, it did teach us a lot. A lot of new Linux users, and a few old-hat users setting up Linux environments, allowed us to be in a MUCH better testing position for issues such as these.
This is part of what we ran over by a little bit: getting some of those major problems resolved, a lot of which came from the still-in-progress SDL implementation, took a good bit of time and work to get in a more acceptable shape. However, with this, it puts us in a better position going forward to streamline and de-gunk a lot of old stuff from the engine - not QUITE yet, but in the near future.
And so, while 3.8 will find itself fairly light-weight on the new and shiney, hopefully everyone that grabs it on our downloads page will find it to be a much more stable platform. We ask that you guys grab it, create some test projects on whatever platforms you have access to, and really rake it over the coals. She's just about ready, but no doubt there are some problems that were missed, and that's where this release candidate comes in.
The RC will run for a week or two to try and squeeze a little bit more polish in, but she's almost there, and we look forward to you guys testing this RC, and then making use of the release!
NOTE: The reason why this is a few days past the 1st, like we were shooting for, is because Linux still lacks save/open dialogs. I've been working to fix this for 3.8, but I've ran into a few problems with it, so it's not currently in the 3.8 RC. I'll keep working on it during the RC testing phase and will have it in for the 3.8 release proper.