| 14 | | * trunk : this is where you can get the most recent changes to the templates. The structure of this branch is a little bit different from other branches, this is a log of every modification made to the templates. Every change is first done in the trunk. This is not guaranteed to work... This branch should not be used as a source for a production SCDB. |
| 15 | | * branches : contains one ''branch'' per middleware version. These branches contain changes merged from the trunk and the branch revision log link to the trunk revisions where the the changes were introduced. What's here is something reasonnably stable, very often announced as pre-releases. '''This is the recommended version to use for production''', in particular for grid templates. It allows to get last updates for critical services like patches, VO parameters, certificates... |
| 16 | | * tags : contains one tag per stable version of the templates. The tag name starts with the middleware release, so it is quite easy to identify what you are looking for. Versions in the tag area are what we call QWG releases. They link to the corresponding branch revision. By definition they are outdated as soon as they are released... |
| | 14 | * [source:templates/trunk trunk]: this is where you can get the most recent changes to the templates. The structure of this branch is a little bit different from other branches, this is a log of every modification made to the templates. Every change is first done in the trunk. This is not guaranteed to work... This branch should not be used as a source for a production SCDB. |
| | 15 | * [source:templates/branches branches]: contains one ''branch'' per middleware version. These branches contain changes merged from the trunk and the branch revision log link to the trunk revisions where the the changes were introduced. What's here is something reasonnably stable, very often announced as pre-releases. '''This is the recommended version to use for production''', in particular for grid templates. It allows to get last updates for critical services like patches, VO parameters, certificates... |
| | 16 | * [source:templates/tags tags]: contains one tag per stable version of the templates. The tag name starts with the middleware release, so it is quite easy to identify what you are looking for. Versions in the tag area are what we call QWG releases. They link to the corresponding branch revision. By definition they are outdated as soon as they are released... |
