Changes between Version 4 and Version 5 of SvnOverview

Timestamp:

02/12/07 01:46:14 (17 years ago)

Author:

arango

Comment:

--

SvnOverview

@@ -47 +47 @@
 
  * Anyone should be able to view the contents of the repository, look at this wiki and view the tickets.
- * A username and password are required to put your changes back into the repository. 
- * To work with data from a repository, you "checkout" a version. 
- * You can check out the most recent version or a specific release, and either the entire repository, or just certain subdirectories. 
+ * A username and password are required to access the repository. 
+ * To work with data from a repository, you '''checkout''' a version.
+ * You can check out the most recent version or a specific release, and either the entire repository, or just certain sub-directories. 
  * Checking a project out makes a copy of the most recent version on the client requesting checkout
- * Svn suggests only checking out into an empty directory
+ * '''svn''' suggests only checking out into an empty directory
 
 '''What you get'''
 
- * If you choose to checkout the project into '''MyDir''' using the second command above, you'll find trunk, branches, and tags directories created in your local directory. Otherwise, if you only checkout the trunk (first command above) the files and sub-directories in the trunk will be created only.
- * Trunk is the main area for development, and unless otherwise instructed, work with the code in trunk
- * Tags will contain stable versions if they exist
- * Branches will have offshoots implementing new functionality- develop in the branch, then merge back into the trunk
+ * If you choose to checkout the project into '''MyDir''' using the second command above, you'll find '''branches''', '''tags''' and '''trunk''' directories created in your local directory. Otherwise, if you only checkout the trunk (first command above) the files and sub-directories below the trunk will be created only.
+ * Trunk is the main area for development, and unless otherwise instructed, work with the code in trunk.
+ * Tags will contain stable frozen versions.
+ * Branches will have offshoots implementing new functionality - develop in the branch, then merge back into the trunk.
  
 '''Work flow'''
 
- * Start each session with update
- * Modify and debug the code locally
- * When you’re done with changes, commit changes to the repository 
- * This will cause the version number to be updated at the repository
- * Repeat
+ * Start each session with update.
+ * Modify and debug the code locally.
+ * When you’re done with changes, commit changes to the repository. 
+ * This will cause the version number to be updated at the repository.
+ * Repeat.
 
 '''Conflict resolution'''