|
Size: 1512
Comment:
|
Size: 2753
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Version Control System for LCGT = This page contains information for using version control system, subversion, for various LCGT tasks. |
= Version Control System for KAGRA = This page contains information for using version control system, subversion, for various KAGRA tasks. |
| Line 8: | Line 8: |
| 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. | 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. |
| Line 10: | Line 10: |
| It is probably easier to illustrate a sample use case with an example. Suppose two people, A and B are working on an interferometer simulation program. The simulation program has three files, file1, file2 and file3. Initially, exact copies of those files are installed to the computers of A and B.<<BR>> Now, A started to edit file1 to implement a new function. About the same time, B started to edit file2 to add his own changes to it. If they continue to work like this for a while, they will eventually have two very different sets of files. There may be some inconsistent changes made by them to their own version of the program. After a while, it will become very difficult to merge their works back to a single program. |
For more detailed reasonings for the use of VCS, see [[/Reasoning|here]]. |
| Line 20: | Line 12: |
| == LCGT SVN quick start == See here. |
== KAGRA SVN Policies == === Basic rules === * 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. === Directory Structure === 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. == Quick Links == KAGRA svn root directory<<BR>> `https://granite.phys.s.u-tokyo.ac.jp/svn/LCGT/` <<BR>> (Not intended for accessing with a web browser. To be used with {{{svn}}} command.) [[https://granite.phys.s.u-tokyo.ac.jp/trac/LCGT|LCGT trac]] [[https://granite.phys.s.u-tokyo.ac.jp/trac/LCGT/browser|LCGT svn repository browser]] [[http://subversion.apache.org/|SVN Web Page]] [[http://svnbook.red-bean.com/en/1.5/index.html|SVN Manual]] [[http://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=5615|SVN installation manual]] (for Windows users only) == KAGRA SVN quick start == See [[/QuickStart|here]]. == Basic work flow of SVN == See [[/WorkFlow|here]]. == Branching and Tagging == See [[/BranchTag|here]]. == trac and tickets == See [[/Trac|here]]. |
Version Control System for KAGRA
This page contains information for using version control system, subversion, for various KAGRA tasks.
Contents
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
Basic rules
- 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.
Directory Structure
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.
Quick Links
KAGRA svn root directory
https://granite.phys.s.u-tokyo.ac.jp/svn/LCGT/
(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
See here.
Basic work flow of SVN
See here.
Branching and Tagging
See here.
trac and tickets
See here.