| 24 | | The preferred development environment is usually for the library being worked on have a development branch checked out, while Boost super-project and other Boost libraries are on the {{{master}}} branch. This causes tests of your library to run against {{{master}}} of other Boost libraries and that is a more realistic test environment in than testing against the possibly unstable {{{develop}}} branch of other Boost libraries. Robert Ramey has advocated this approach to testing for years, and Git and the modularization of Boost via submodules makes this approach easier. |
| 25 | | |
| 26 | | === Update super-project and submodules for all libraries === |
| | 24 | The preferred development environment is usually for the library being worked on have a development branch checked out, while other Boost libraries are as pointed to by the Boost super-project {{{master}}} branch. This causes local tests of your library to run against {{{master}}} for other Boost libraries as last accepted by the Boost super-project. |
| | 25 | That is a more realistic test environment in than testing against the possibly unstable {{{develop}}} branch of other Boost libraries or against the {{{master}}} branch of other libraries as of a different point in time than that seen by the super-project. Robert Ramey has advocated this approach to testing for years, and Git and the modularization of Boost via submodules makes this approach easier. |
