If you’ve been watching our enthought-dev mailing list, ‘m sure you’ve noticed that a large number of people have been working on making sure that all the unit tests and examples in the ETS projects “just work”. For tests, that means they either pass or get skipped by the test suite collector, and that you can run them by doing ‘python setup.py test’ for the project. For examples, that means invoking the example module using the python interpreter. This effort is part of our push to release ETS 3.0 ASAP — we’re trying very hard to have it out before SciPy (mid-August). I apologize for the late public notice about this — I’m not sure how I skipped announcing it as I’ve been talking about it internally here for more than a month!
* We are aiming for a FULL ETS 3.0b1 BETA RELEASE BY EARLY NEXT WEEK, Tuesday, July 29th.
* We are also aiming for a TRAITS 3.0 *RELEASE* BY THE END OF THIS WEEK, Friday, July 25th.
* Following the ETS 3.0b1 release, we will take a week to do more testing and fix outstanding bugs, and if need be release a 3.0b2 release on Tuesday, August 5th. If that happens, the official release of ETS 3.0 will then be Tuesday, August 12th. If not, it will be August 5th.
BTW: I’m setting up milestones in the Enthought Trac (not done yet at the time of this post) to document the efforts needed to hit these dates. If you want to help us out by testing and/or fixing issues (feel free to submit patches in tickets!), please make sure to enter any issues you discover in the next earliest milestone.
Please provide feedback ASAP if you are involved in something that will make it difficult to meet this schedule!