On 22 July 2011 08:27, Mark Evenson evenson@panix.com wrote:
Is there anybody with any remaining issues or fixes up his sleeve? Anybody wants to report an issue with the current 0.26.x branch? If not, I'm planning to roll the 0.26.1 release mid next week.
I believe we are still out two ANSI regressions due to the #\Unnnn syntax added to the reader for Unicode characters, but I haven't really had time to check in the past few days (vacation!), but I should be able to get to this over the next few days.
According to a test run I did last night, we don't have regressions compared to 0.25. Our current failure count is 22, not counting ensure-directories-exist because I didn't remove the scratch directory, and the previous count was 30, so we got a pretty nice improvement from the printing fixes. We did try and rush the release a bit, I suppose, but we picked up nicely.
I think we should just release it, and look at the next milestones, which in my mind would be roughly
1) strive for sub-20 failures, there's a couple that should be pretty straightforward although not trivial (clos, make-condition) 2) find out why our build nowadays takes 7 minutes, we used to be able to do it in 2 minutes. Something(s) has increased the build time quite a bit. 3) take a look at defstruct, it looks visibly slow when looking at the tests progressing
And of course any other improvements that scratch people's itches. :) All in all it looks to be in a good shape.