Putting your project under version control - Revision history

Admin: /* What is Version control system ? */

2011-02-25T09:57:35Z

‎What is Version control system ?

Admin at 14:21, 24 February 2011

2011-02-24T14:21:52Z

Admin: /* Further reading */

2011-02-24T14:21:39Z

‎Further reading

Admin at 14:18, 24 February 2011

2011-02-24T14:18:20Z

Admin at 14:16, 24 February 2011

2011-02-24T14:16:01Z

Admin at 14:15, 24 February 2011

2011-02-24T14:15:48Z

Admin at 14:12, 24 February 2011

2011-02-24T14:12:42Z

Admin: moved Putting projects under version control to Putting your project under version control

2011-02-24T14:06:05Z

moved Putting projects under version control to Putting your project under version control

Admin: /* What is Version control ? */

2011-02-24T14:04:54Z

‎What is Version control ?

Admin at 14:03, 24 February 2011

2011-02-24T14:03:10Z

@@ Line 16: / Line 16: @@
 ===What is Version control system ?===
-* a place to store all the various revisions of the files your write while developing an application.
+* a place to store all the various revisions of the files you write while working on your project
-* it all goes to '''repository''', a central place that holds the master copy of all versions of your files.
+* it all goes to '''repository''', a central place that holds the master copy of all versions of your files
 * should be safe, secure, reliable, gets backed up regularly

← Older revision		Revision as of 14:21, 24 February 2011
Line 1:		Line 1:
−	~~__NOTOC__~~
	==Introduction to Version control==		==Introduction to Version control==

@@ Line 42: / Line 42: @@
 ==Further reading==
+* http://en.wikipedia.org/wiki/Revision_control
+* http://en.wikipedia.org/wiki/Comparison_of_revision_control_software
 [[Category:Qualiteam services]]

@@ Line 11: / Line 11: @@
 * gives a project-wide undo button; nothing is final, and mistakes are easily rolled back
 * allows multiple developers to work on the same code base in a controlled manner
 * keeps a record of the changes made over time
 * works as a project-wide time machine, allowing you to dial in a date and see exactly what the project looked like on that date
@@ Line 21: / Line 18: @@
 * a place to store all the various revisions of the files your write while developing an application.
 * it all goes to '''repository''', a central place that holds the master copy of all versions of your files.
 * should be safe, secure, reliable, gets backed up regularly
@@ Line 35: / Line 30: @@
 ===Basic terminology===
 ==How to put your project under version control==

← Older revision		Revision as of 14:16, 24 February 2011
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
−
−
	==Introduction to Version control==		==Introduction to Version control==

@@ Line 1: / Line 1: @@
 __NOTOC__
 If you’ve used Microsoft Word or Excel, OpenOffice or any of the like, you may already be familiar with a process called '''version control''' or '''revision control'''. It’s the management of the changes made to a document by creating different or new versions each time it’s modified, and allows you to revert to any previous version if needed; some programs also allow you to merge versions. This is usually implemented on documents where changes are made often or if it’s being worked on by multiple people in a team.
@@ Line 6: / Line 10: @@
 There are different models of software available, which vary depending on how the information is shared. The deciding factors as to which VCS model to use depend on the type of project and amount of collaboration that will take place, as well as preference of a centralized system versus a peer-to-peer approach.
-==Why Version control ?==
+===Why Version control ?===
 * gives a project-wide undo button; nothing is final, and mistakes are easily rolled back
@@ Line 16: / Line 20: @@
 * works as a project-wide time machine, allowing you to dial in a date and see exactly what the project looked like on that date
-==What is Version control system ?==
+===What is Version control system ?===
 * a place to store all the various revisions of the files your write while developing an application.
@@ Line 24: / Line 28: @@
 * should be safe, secure, reliable, gets backed up regularly
-==What to store ?==
+===What to store ?===
 * Source code
@@ Line 31: / Line 35: @@
 * Significant emails, minutes of meetings, info from the Web
-==Basic terminology==
+===Basic terminology===
 '''Working copy''': local copy of all the things we need from the repository to work on our part of the project.
@@ Line 40: / Line 44: @@
 '''Update''': receive the latest set of files from repository.
 ==Further reading==
 [[Category:Qualiteam services]]

← Older revision		Revision as of 14:12, 24 February 2011
Line 42:		Line 42:

	==Further reading==		==Further reading==
		+
		+	[[Category:Qualiteam services]]

← Older revision	Revision as of 14:06, 24 February 2011
(No difference)