Changes between Version 5 and Version 6 of BoostSubversion


Ignore:
Timestamp:
May 10, 2007, 5:26:26 PM (15 years ago)
Author:
Douglas Gregor
Comment:

Move sandbox information to another page

Legend:

Unmodified
Added
Removed
Modified
  • BoostSubversion

    v5 v6  
    1919 * `stable`: Contains the latest "stable" version of Boost.
    2020 * `devel`: Contains the latest "development" version of Boost. This branch will typically be more volatile than the `stable` branc.
    21  * `sandbox`: Contains libraries and tools that are under active development and have not yet been reviewed or accepted into Boost. See below for information about organization of the sandbox.
     21 * `sandbox`: Contains libraries and tools that are under active development and have not yet been reviewed or accepted into Boost. See BoostSandbox for information about organization of the sandbox.
    2222 * `website`: Contains the upcoming Boost web site, which is not yet live.
    2323 * `branches`: Contains various branches of Boost libraries, typically for non-trivial changes to Boost libraries that need to be made separately from the `devel` branch.
     
    4040To receive e-mail each time a change is committed to the Boost Subversion repository, join the Boost-commit mailing list at http://lists.boost.org/mailman/listinfo.cgi/boost-commit
    4141
    42 == Sandbox Organization ==
    43 The Boost Sandbox (housed in the `sandbox` subdirectory of the Subversion repository) contains unreviewed code that is intended to eventually become a part of the Boost libraries. Because there are typically many projects in the sandbox at any one time (in various stages of development), the sandbox should be organized by project. Each project should have its own subdirectory inside `sandbox`. For example, a new XML library would reside in `sandbox/xml`. Inside that project-specific subdirectory, the project should be organized like any other Boost library, with a `boost` subdirectory (for headers) and `libs` subdirectory (for source code, build files, and documentation). Our hypothetical XML project would likely have the following structure:
    44 
    45     sandbox/xml/
    46        boost/ - Contains xml.hpp, which includes all of the headers from xml/
    47           xml/ - Contains Boost.XML headers
    48        libs/
    49           xml/
    50             build/ - Contains Jamfiles to build Boost.XML
    51 
    52             doc/ - Contains documentation for Boost.XML
    53 
    54             src/ - Contains Boost.XML compiled source files
    55    
    56 Many existing projects in the sandbox do not follow this structure, opting to place headers in `sandbox/boost` and supporting files in `sandbox/libs`. We encourage developers to migrate these projects to the project-centric organizational structure.
    57 
    58