| 12 | | You can review the current status of modularization [http://bbot.boostpro.com/waterfall?show_events=true&builder=Boost.Modularize-x-Modularize&builder=Boost-vc8-win64-Integration&builder=Boost-vc7.1-win64-Integration&builder=Boost-gcc-linux-Integration&builder=Boost-vc10-win64-Integration&builder=Boost-vc9-win64-Integration&reload=none here]. |
| | 12 | [http://github.com/boost-lib/boost Modularized Boost] is continuously maintained and tested by a system that automatically does two things: |
| | 13 | |
| | 14 | 1. **Modularization**: shuffle files from their standard places in a Boost distribution into separate [http://github.com/boost-lib per-library git repositories] |
| | 15 | 2. **Integration Testing**: run each libraries' tests to make sure its modularized state is healthy. |
| | 16 | |
| | 17 | You can review the current status of these steps [http://bbot.boostpro.com/waterfall?show_events=true&builder=Boost.Modularize-x-Modularize&builder=Boost-vc8-win64-Integration&builder=Boost-vc7.1-win64-Integration&builder=Boost-gcc-linux-Integration&builder=Boost-vc10-win64-Integration&builder=Boost-vc9-win64-Integration&reload=none here]. The rest of this section details what the steps are doing. |