David Abrahams wrote:
on Mon Nov 26 2007, Beman Dawes <bdawes-AT-acm.org> wrote:
The merge into branches/release "from" point was the 1.34.1 release. The "to" point was the trunk at revision 41356.
This is very similar to a traditional *branch* for release. The effective difference is that a library can be easily reverted to 1.34.1.
Hopefully, no libraries will have to be reverted. But we will do just that for any libraries not ready in the next ten days. The Unresolved Issues reports should now be reflecting the high-priority platforms the release managers will be using to make that determination.
What does this mean for the SunPro workarounds I'm implementing that make Boost.Python work on that compiler?
Go ahead and merge. See my post "[1.35.0] branches/release open for known-good merges". I'll try to expand on that post a bit so the plan is clearer. --Beman