For lack of any strong consensus, I made the decision to unleash 1.1.8 for Windows on the world. Remember that sb-concurrency is broken, so if you care about that, don't upgrade. (Or better: provide a patch so that we can get this fixed.) I am hoping that the majority of Windows users do not yet depend on this feature and thus will be able to upgrade without trouble.

On Windows, sb-concurrency continues to be broken. Does this actually affect anyone? Will anyone object if I make a Windows release this time (without sb-concurrency)? I don't like the idea of have a major platform go untested for so long, so I'd like to get this back in the hands of users.

Unfortunately, I *still* don't have time to actually investigate the source of the problem. :P

If the version number were going by substantial changes, then this one
might be sbcl-1.2.rc1. It's been a busy month, with lots of fixes and
new features all over the tree: for the next short period it would be
truly excellent to test those new features against all the code out
there, watching particularly for any regressions on real code. I aim to
make the release during the second half of next week.