Changes between Version 3 and Version 4 of SCS_REPO_MAINTENANCE_R3

Timestamp:

01/19/09 11:33:57 (16 years ago)

Author:

todor

Comment:

--

SCS_REPO_MAINTENANCE_R3

@@ -23 +23 @@
 Explain where the tag is, any new rules added to the [wiki:PLATFORM_STANDARDS_REPOSITORY]
 = Design =
+ * Read thoroughly and check [wiki:PLATFORM_STANDARDS_REPOSITORY] for mistaken links and fix them.
+ * Tag and branch are basically same things so you will need to create one branch for the release team where their fixes are going to be applied and one tag for iteration 03 for backup purposes. Use the instructions below to create the branch and the tag in implementation of this task.
+ * Read the section about creating a tag using TortoiseSVN or creating a tag on Linux
+==== Creating Tag ====
+Another common version control concept is a tag. A tag is just a “snapshot” of a project in time. In Subversion, this idea already seems to be everywhere. Each repository revision is exactly that—a snapshot of the filesystem after each commit.
 
+However, people often want to give more human-friendly names to tags, like release-1.0. And they want to make snapshots of smaller subdirectories of the filesystem. After all, it's not so easy to remember that release-1.0 of a piece of software is a particular subdirectory of revision 4822.
+ * How to create a tag on Linux
+{{{
+$ svn copy svn://asteasolutions.net/sophie2-repo/trunk \
+           svn://asteasolutions.net/sophie-jr/tags/m??-??? \
+      -m "Comment."
+Committed revision 351.
+}}}
+
+Here m??-??? stands for the milestone and its name for example m01-pre1.[[BR]]
+After the copy completes, the new m??-??? directory is forever a snapshot of how the project looked in the HEAD revision at the time you made the copy. Of course you might want to be more precise about exactly which revision you copy, in case somebody else may have committed changes to the project when you weren't looking. So if you know that revision 350 of /sophie2-repo/trunk is exactly the snapshot you want, you can specify it by passing -r 350 to the svn copy command. In Subversion, there's no difference between a tag and a branch. Both are just ordinary directories that are created by copying. Just as with branches, the only reason a copied directory is a “tag” is because humans have decided to treat it that way: as long as nobody ever commits to the directory, it forever remains a snapshot. If people start committing to it, it becomes a branch.
+
+ * How to create a tag on Windows with [http://tortoisesvn.net/downloads TortoiseSVN]:
+  * Update first.
+  * Go to "trunk" folder in your local repository
+  * Right click on it
+  * TortoiseSVN -> Branch/tag
+  * Dialog window appears. Now instead of svn://sophie.org/sophie2/trunk (or svn://asteasolutions.net/sophie-jr/trunk) use svn://sophie.org/sophie2/tags/m??-??? (or svn://sophie.org/sophie2/tags/m??-???). Here m??-??? stands for the milestone and its name for example m01-pre1.
+  * It is obligatory to write a comment when you commit.
+  * Tags must be created at the end of each iteration when the work is frozen.
+  * You can download TortoiseSVN from [http://tortoisesvn.net/downloads here].
+ * Follow the steps carefully
+ * If there are mistakes or some incomplete things leave a comment
+ * Create tag for iteration m02b following the instructions
+ * Create accounts for new members that haven't such
+ * The tag must be created in svn://sophie2.org/sophie2/tags/m02b-pre02b (where is located the new repository)
 = Implementation =
 ^(Implementation results should be described and linked here (from the wiki or the repository))^