Version Control System for KAGRA
This page contains information for using version control system, subversion, for various KAGRA tasks.
Introduction, why version control system ?
Version control system (VCS) is a computer tool to manage the history of various files you work on. Usually, files are documents or program codes, but you can use it for managing virtually any type of files. It keeps track of the changes you make to the files and let you roll back to any previous version if you want. The VCS is particularly useful when several people are working on a single set of files, for example, a group of people writing a paper, or several people developing a simulation code together. Subversion (svn) is a popular VCS and used by many projects around the world. There is an svn repository for KAGRA. KAGRA collaborators are strongly encouraged to use this svn repository for any applicable tasks.
For more detailed reasonings for the use of VCS, see here.
KAGRA SVN Policies
- Feel free to use SVN. Don't be afraid of commit. You can always rollback your changes.
- Always add comments when you commit changes.
- Create a ticket when you want to make a major change or find a problem. Make sure to put the email addresses of the people who will should be notified of the change or the problem in the CC field of the ticket properties.
- Create branch if you want to make large changes.
There are three directories in the top directory of the KAGRA SVN.
trunk/ branches/ tags/
trunk is the directory you want to put most files. Please make sub directories under trunk (preferably under each subsystem's directory).
branches and tags are the directories for putting branched or tagged trees. When you make a branch or tag, please use these directories.
KAGRA svn root directory
(Not intended for accessing with a web browser. To be used with svn command.)
SVN installation manual (for Windows users only)
KAGRA SVN quick start
Basic work flow of SVN
Branching and Tagging
trac and tickets