On Fri, May 17, 2013 at 5:48 AM, Anselm Kruis <[email protected]> wrote: > Stackless Python 2.7.4 and 2.7.5 are both ready to be released. If there are > no last minute bug reports, I'll push them to hg.python.org/stackless > tomorrow morning. > > Sorry for the tight schedule, but I need 2.7.5 properly integrated into our > workflow tool next Tuesday.
Sounds great, thanks for doing this Anselm. What testing do you put the code through before release? I used to do something like: - Build the "to be released" source code with visual studio as STACKLESS in release and debug modes, run the unit tests for Python and Stackless in each. We've had bugs in the past that only came up in debug builds. - Build the "to be released" source code with visual studio as STACKLESS_OFF, run the unit tests for Python. - Build the source code release for the given Python version with visual studio, run the unit tests for Python. Verify that the failures on my Windows 7 machine would match those for the STACKLESS compile test results. This was necessary because there would always be unit test failures on my machine for the official Python souce code release. - Build the "to be released" source code with mingw on my machine, run the Python and Stackless unit tests. - Build the "to be released" source code on a linux box, run the Python and Stackless tests. I think we should consider whether we need to do all these, and perhaps automating the process to save on all the manual work I used to do. Thoughts? Cheers, Richard. _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
