General day to day - Revision history

Jprenaud at 17:45, 8 February 2006

2006-02-08T17:45:39Z

2006-02-08T17:44:32Z

2006-02-07T14:14:54Z

2006-02-07T14:14:21Z

2006-02-07T13:45:47Z

2006-02-06T19:23:47Z

2006-02-06T19:21:34Z

2006-02-06T18:40:24Z

New page

This is for info on the principles of using version control day to day

← Older revision		Revision as of 14:14, 7 February 2006
Line 1:		Line 1:
−	~~Rough..This is for info on the principles of using version control day to day~~

−	=A Working Cycle=	+	=The Working Cycle=

	When using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code. You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to. Finally, if you are staisfied, you will then want to create a new latest version of the code which incorporates your changes.		When using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code. You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to. Finally, if you are staisfied, you will then want to create a new latest version of the code which incorporates your changes.

@@ Line 11: / Line 11: @@
 Thus, your normal working cycle will be:
 # new copy/update
 # test
@@ Line 16: / Line 17: @@
 # test
 # commit
 You can learn how to do this with Subversion by clicking here (link).

@@ Line 3: / Line 3: @@
 =A Working Cycle=
-When you are using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code.  You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to.  Finally, if you are staisfied, you will then want to incorporate your changes into a new latest version of the code.
+When using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code.  You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to.  Finally, if you are staisfied, you will then want to create a new latest version of the code which incorporates your changes.
-If you are working collaboratively, it is also a good idea to check that the latest version of the code is working correctly when take a local copy.  Also, you may already have a local copy of the code.  You will want to update your local copy with any changes committed to the repository since you last updated.
+If you are working collaboratively, it is also a good idea to check that the latest version of the code is working as it should '''before''' you make any changes.  This has been found from experience, to greatly protect your sanity!
 Thus, your normal working cycle will be:
-# checkout/update
+# new copy/update
 # test
 # edit

← Older revision		Revision as of 19:23, 6 February 2006
Line 14:		Line 14:
	# test		# test
	# commit		# commit
		+
		+	You can learn how to do this with Subversion by clicking here (link).

← Older revision		Revision as of 19:21, 6 February 2006
Line 1:		Line 1:
		+	Rough..This is for info on the principles of using version control day to day

−	~~This~~ is ~~for info on~~ the ~~principles~~ of ~~using~~ version ~~control day~~ to ~~day~~	+	=A Working Cycle=
		+
		+	When you are using a version control system, the first thing you will typically want to do is to obtain a copy of the latest version of your code. You will then, no doubt, want to edit your local copy of the code and then test that your changes are doing what you wanted them to. Finally, if you are staisfied, you will then want to incorporate your changes into a new latest version of the code.
		+
		+	If you are working collaboratively, it is also a good idea to check that the latest version of the code is working correctly when take a local copy. Also, you may already have a local copy of the code. You will want to update your local copy with any changes committed to the repository since you last updated.
		+
		+	Thus, your normal working cycle will be:
		+
		+	# checkout/update
		+	# test
		+	# edit
		+	# test
		+	# commit