| 1 | = Subversion Repository = |
| 2 | |
| 3 | Boost uses [http://subversion.tigris.org/ Subversion] to manage all of the data associated with Boost's development, including the source code to Boost, documentation for Boost libraries, and the Boost web site. |
| 4 | |
| 5 | == Accessing the Boost Subversion Repository == |
| 6 | The Subversion repository can be accessed in several ways: |
| 7 | |
| 8 | * Anonymous, read-only access to the Boost Subversion repository is available at http://svn.boost.org/svn/boost. To access the latest stable branch of Boost, for instance, one would check out from http://svn.boost.org/svn/boost/stable. For example, using the command-line `svn`, one might use: |
| 9 | |
| 10 | svn co http://svn.boost.org/svn/boost/stable boost-stable |
| 11 | |
| 12 | * Developer (read/write) access to the Boost Subversion repository is available for Boost contributors at https://svn.boost.org/svn/boost. For information about gaining developer access to the Boost Subversion repository, see below. |
| 13 | |
| 14 | * The Subversion repository can be browsed online at http://svn.boost.org/trac/boost/browser. |
| 15 | |
| 16 | == Organization of the Boost Subversion Repository == |
| 17 | The Boost Subversion repository is organized into several top-level directories, reflecting various stages of Boost library development and subtasks within the Boost community. We have the following top-level directories: |
| 18 | |
| 19 | * `stable`: Contains the latest "stable" version of Boost. |
| 20 | * `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. |
| 22 | * `website`: Contains the upcoming Boost web site, which is not yet live. |
| 23 | * `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. |
| 24 | * `tags`: Contains "tags" that mark certain points in the source tree, such as particular Boost releases. |
| 25 | * `sandbox-branches`: Similar to `branches`, but for code that resides in the `sandbox`. |
| 26 | * `sandbox-tags`: Similar to `tags, but for code that resides in the `sandbox`. |
| 27 | |
| 28 | == Developer Access to Subversion == |
| 29 | Boost contributors are given read/write access to the Boost Subversion repository when their Boost tasks warrant. There are three different areas of the Boost Subversion repository that contributors may need access to: |
| 30 | |
| 31 | * The main Boost development areas, including the `devel` and `stable` directories. This level of access is typically restricted to authors and maintainers of Boost libraries. |
| 32 | * The `sandbox` area, which is used to develop new libraries and tools that have not yet come up for Boost review. This level of access is available to contributors who want to develop future Boost libraries and collaborate with other Boost contributors. |
| 33 | * The web site, which stores the Boost web site. |
| 34 | |
| 35 | To gain developer access to the Boost Subversion repository, please send a email to the [http://www.boost.org/more/moderators.html Boost Moderators] at `boost-owner -at- lists.boost.org` stating why you need write access to the Boost Subversion repository, and which parts of the repository--boost itself, the sandbox, or the web site--you need access to. Once a moderator has approved you for access to the Subversion repository, you will receive an invitation via e-mail that asks you to provide a user name and a password, which will be used to access both the Boost Subversion repository and the Boost Trac. You will also be asked to grant permission for your past and future Boost contributions to be licensed under the [http://www.boost.org/more/license_info.html Boost Software License] version 1.0 and future versions: your permission is required to work with the Boost Subversion repository, so that we can ensure that Boost code is licensed under the Boost Software License. |
| 36 | |