Difference between revisions of "Wales Group Version control"
Jump to navigation
Jump to search
import>Cen1001 m (Version control moved to Wales Group Version control) |
import>Csw34 |
||
| Line 1: | Line 1: | ||
| + | We are now in the final stages of putting the group code under version control. GMIN and PATHSAMPLE, along with the CHARMM and AMBER code used with them have been added to the repository. OPTIM will be added soon. Once stable versions of the source code have been added - the next step is to set up the nightly test suite for each code, and move the documentation into the repository. |
||
| − | Currently Szilard is trailing version control on his version of PATHSAMPLE with Chris. |
||
| + | RSS feeds are generated every 10 minutes from the SVN log files. There is more info here (INSERT LINK) |
||
| − | If the trail shows that using SVN would be beneficial to the development of GMIN, OPTIM and PATHSAMPLE then it may be rolled out to cover them all. |
||
| + | |||
| + | ==Usage tips== |
||
| + | Make sure you followed the setup instructions on the group SVN page (INSERT LINK). The procedure includes setting up a template file. This ensures that all posts are in the same basic format! |
||
| + | |||
| + | In general you should: |
||
| + | * run 'svn update' on a regular basis to ensure you have the latest bug fixes |
||
| + | * '''always''' do an 'svn update' before you do 'svn commit' |
||
| + | * commit your changes regularly. If you wait a two months before commit your changes, you're likely to have to resolve more conflicts in parts of the code that has been changed by others in the meantime. |
||
| + | * if you get a conflict (C flag) when running 'svn update', find out who introduced the change and talk to them about it. |
||
Revision as of 16:12, 11 July 2008
We are now in the final stages of putting the group code under version control. GMIN and PATHSAMPLE, along with the CHARMM and AMBER code used with them have been added to the repository. OPTIM will be added soon. Once stable versions of the source code have been added - the next step is to set up the nightly test suite for each code, and move the documentation into the repository.
RSS feeds are generated every 10 minutes from the SVN log files. There is more info here (INSERT LINK)
Usage tips
Make sure you followed the setup instructions on the group SVN page (INSERT LINK). The procedure includes setting up a template file. This ensures that all posts are in the same basic format!
In general you should:
- run 'svn update' on a regular basis to ensure you have the latest bug fixes
- always do an 'svn update' before you do 'svn commit'
- commit your changes regularly. If you wait a two months before commit your changes, you're likely to have to resolve more conflicts in parts of the code that has been changed by others in the meantime.
- if you get a conflict (C flag) when running 'svn update', find out who introduced the change and talk to them about it.