16 | | * The code for each release is 'tagged'. For example, the code for version 6.3.14 is tagged with '''boinc_core_release_6_3_14'''. |
17 | | * A 'branch' is created for each released minor version. For example, the branch '''boinc_core_release_6_2''' is the code for the latest release of version 6.2. |
| 16 | * The code for each release is 'tagged'. |
| 17 | For example, the code for version 6.3.14 is tagged with '''boinc_core_release_6_3_14'''. |
| 18 | * A 'branch' is created for each released minor version. |
| 19 | For example, the branch '''boinc_core_release_6_2''' is the code for the latest release of version 6.2. |
21 | | For all software other than the client (i.e., server, web, and API) the latest "stable" version |
22 | | is kept in a branch, '''server_stable'''. |
| 23 | For all software other than the client (i.e., server, web, and API) |
| 24 | a "stable" version is kept in a branch, '''server_stable'''. |
| 25 | Don't use the server software in a client tag or branch; it probably isn't stable. |
24 | | '''NOTE: don't use the server software in a client tag/branch; it probably isn't stable.''' |
| 27 | Notes: |
| 28 | * There is no formal testing process for server software. |
| 29 | Every so often, when no bugs have been reported recently, |
| 30 | we copy trunk to server_stable. |
| 31 | * Because of limited resources, bug fixes to server software are normally |
| 32 | NOT back-ported from trunk to server_stable. |
| 33 | |
| 34 | For these reasons: '''trunk is typically a better choice |
| 35 | than server_stable for server software'''. |