How about we target the next release freeze/start-of-test for Nov 5? Between now and the next release, Thilo wants to do work on CAS refactoring - to enable that, I suggest we agree to freeze **now** in the trunk all feature enhancement/improvement changes, and only do bug fixes (unless the changes are completely independent of Thilo's work - such as for example adding some documentation to a non-CAS area). The goal is to allow Thilo to "branch" the code base and do his work in parallel, with minimal (we hope) impact on the future "merging".
We need a release manager for the next release. This involves reading some web pages to see that we follow the right process, and then reminding the others in the dev community to help out with testing, etc. This work would start in November. For our first 2 releases, Thilo has volunteered, (Thank You!), but I'm guessing he'd be happy for someone else to take a turn. Any volunteers? -Marshall
