Until further notice, the plan is to do quarterly Boost releases, and stick to that schedule even if updates for particular libraries aren't ready. If a library on the trunk isn't ready for a release, the prior release will be used for that library. I hoping for a final cut-off date of Friday, October 19, for making "go/no-go" decisions on which library updates make it into 1.35.0. That means libraries with updates to be included should be passing regression tests on trunk well before then. The process of merging into the release branch will start sooner for libraries already ready. Here is what developers should be doing over the next two weeks: * Start watching the regression tests at http://beta.boost.org/development/tests/trunk/developer/summary.html * For release criteria compilers, fix or markup all failures caused by your library's code. Fix or markup failures caused by your library's code for other compilers according to your own judgment. * For release criteria compilers show failures you think are caused by some other library's code, or by test configuration problems, post list notifications directed at the library or tool causing the problem. For other compilers, do the same if you wish. * For testing on the trunk to be a reliable indicator of release stability, prerequisite libraries on the trunk must be ready for release. If the trunk for your library isn't going to be ready in time for this release, please make a branch of the trunk with your library's name, and "merge" the trunk for your library so it is identical to 1.34.1. Note that if other libraries depend on your library, and you library is causing those libraries to break, you need to fix the trunk or return it to 1.34.1 within the next few days so that you don't impede the other libraries. Now the fun begins, --Beman