On Fri, Mar 22, 2013 at 10:54 AM, Elliott Slaughter <firstname.lastname@example.org> wrote:
On Fri, Mar 22, 2013 at 9:22 AM, Christophe Rhodes <email@example.com> wrote:Hi all,
In accordance with the weather here in London, I would like to declare a
freeze on development for release of sbcl-1.1.6 in the next week or so.
Test test test, report any breakage, and satisfy yourselves and everyone
else that everything is marvellous. (Reports to the contrary
accompanied by tasteful, well-crafted patches are acceptable too.)The test failures in sb-concurrency that I reported after 1.1.5 was released still appear to be present, although my more recent testing has shown that the failures are intermittent (frequent, but not 100% reproducible). I unfortunately don't have time to do any meaningful debugging on this before release; I'll be away from my Windows machine all of next week and won't be able to test anything, even if others contribute fixes.I might be able to release a "good" build for Windows for 1.1.6 (i.e. one where the test suite claimed to pass), although I'm not sure we really want to unleash a potentially buggy sb-concurrency on the world.Here is the build log, in case anyone is interested:
"Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay