26 | | The preferred environment for working on a library is to have {{{develop}}} or some other development branch checked out, while other Boost libraries are as defined 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. |
27 | | Thid 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. |
| 26 | The preferred environment for working on a library is to have {{{develop}}} or some other development branch checked out, while other Boost libraries are as defined by the Boost super-project {{{master}}} branch. This causes local tests of your library to run against {{{master}}} for other Boost libraries at the point in time referenced by the Boost super-project. |
| 27 | This 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 at a different point in time than that referenced by the super-project. Robert Ramey has advocated this approach to testing for years, and Git plus Modular Boost makes this approach relatively easy and fast. |