| 36 | === Subprojects organization === |
| 37 | |
| 38 | ''The organization presented here is based on the discussion in the boost devel |
| 39 | list about the best way to organize the main boost repository. Since we have to |
| 40 | define the way we will work, this subprojects can be used as a proof of concept.'' |
| 41 | |
| 42 | Projects like the translation effort are being committed directly to the boost docs |
| 43 | project trunk placed at: |
| 44 | |
| 45 | [http://svn.boost.org/trac/boost/browser/sandbox/boost_docs/trunk https://svn.boost.org/svn/boost/sandbox/boost_docs/trunk] |
| 46 | |
| 47 | This is done for the sake of simplicity. Docs can not affect the work of other people. |
| 48 | |
| 49 | With subprojects, if we commit a buggy version to the trunk we can bother other |
| 50 | people work. To avoid this, we will use the trunk as a merging repository. |
| 51 | Each subproject will have his own repository placed at: |
| 52 | |
| 53 | [http://svn.boost.org/trac/boost/browser/sandbox/boost_docs/subprojects https://svn.boost.org/svn/boost/sandbox/boost_docs/subprojects] |
| 54 | |
| 55 | The organization will be the same for each subproject |
| 56 | |
| 57 | * '''''subproject_name''''' |
| 58 | |
| 59 | * '''branches''' |
| 60 | |
| 61 | * '''tags''' |
| 62 | [[Br]]We will use dates to specify not so buggy versions with the format: ''subproject_name''_{year}_{month}_{day} |
| 63 | [[Br]]Example: boostbook_07_06_28 |
| 64 | |
| 65 | * '''trunk''' |
| 66 | [[Br]]Development branch for the subproject. |
| 67 | |
| 68 | * '''doc''' |
| 69 | |
| 70 | * '''example''' |
| 71 | |
| 72 | * '''test''' |
| 73 | |
| 74 | There are some subprojects that must be integrated in the boost docs trunk repository, |
| 75 | like Improving Boostbook and stylesheets projects. |
| 76 | When you feel confident with a given version, you just copy the last tag of your |
| 77 | subproject to the main trunk. |
| 78 | |
| 79 | Each subproject have a Wiki page with additional information. |
| 80 | |
| 81 | ---- |
| 82 | |