RevisionControl - Revision history

Wickr: Reverted edits by 194.44.144.2 (Talk); changed back to last version by 190.1.20.183

2009-07-31T22:56:27Z

Reverted edits by 194.44.144.2 (Talk); changed back to last version by 190.1.20.183

194.44.144.2: /* What is Revision Control */

2009-07-31T22:34:46Z

‎What is Revision Control

190.1.20.183: /* What system? */ fixed typo

2009-07-22T16:53:48Z

‎What system?: fixed typo

Jrochkind: /* What system? */

2009-03-04T23:53:18Z

‎What system?

96.234.238.227 at 15:03, 4 March 2009

2009-03-04T15:03:59Z

96.234.238.227 at 15:03, 4 March 2009

2009-03-04T15:03:22Z

141.211.43.192: Finished last sentence.

2009-02-16T15:05:02Z

Finished last sentence.

Edsu at 13:23, 10 February 2009

2009-02-10T13:23:01Z

Edsu: added some stuff about revision control

2009-02-10T13:20:18Z

added some stuff about revision control

New page

When you start out on a software project it is really important that you use some form of revision control for your code base. Even if you are the only developer on the project you will want to be able to roll back to previous versions of your software. As your project grows you'll want to involve more people, perhaps from other organizations, and being able to offer them a code repository to interact with is key.

There are lots of choices about what sort of revision control system to use. The key decision is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your code, into their own repository, and, where they can push back changes, or make them otherwise available to you. While there are lots of options for both flavors, Subversion and Git are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub]

@@ Line 1: / Line 1: @@
 [[Category:Patterns]]
-Wa3dU  <a href="http://gquyidobcfhp.com/">gquyidobcfhp</a>, [url=http://nsuwakykkyre.com/]nsuwakykkyre[/url], [link=http://chrvrxqrierb.com/]chrvrxqrierb[/link], http://bzrcnulopmro.com/
+==What is Revision Control==
 ==What to release==

@@ Line 1: / Line 1: @@
 [[Category:Patterns]]
-==What is Revision Control==
+Wa3dU  <a href="http://gquyidobcfhp.com/">gquyidobcfhp</a>, [url=http://nsuwakykkyre.com/]nsuwakykkyre[/url], [link=http://chrvrxqrierb.com/]chrvrxqrierb[/link], http://bzrcnulopmro.com/
-−
-When you start out on a software project it is really important that you use some form of revision control for your code base. Even if you are the only developer on the project you will want to be able to roll back to previous versions of your software, and to tag releases for production. As your project grows you'll want to involve more people, perhaps from other organizations, and being able to offer them a code repository to interact with is key.
 ==What to release==

@@ Line 11: / Line 11: @@
 ==What system?==
-There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.
+There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your code into their own repository, and make them otherwise available to you and others as needed.
 While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub] provide free, rock-solid svn and git repositories, respectively, for any open source project that wants it.

← Older revision		Revision as of 23:53, 4 March 2009
Line 13:		Line 13:
	There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.		There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.

−	While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub] provide free, rock-solid svn and git repositories, respectively, for ~~anyone who~~ wants ~~one~~.	+	While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub] provide free, rock-solid svn and git repositories, respectively, for any open source project that wants it.

← Older revision		Revision as of 15:03, 4 March 2009
Line 1:		Line 1:
		+	[[Category:Patterns]]
		+
	==What is Revision Control==		==What is Revision Control==

← Older revision		Revision as of 15:05, 16 February 2009
Line 3:		Line 3:
	There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.		There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.

−	While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub]	+	While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub] provide free, rock-solid svn and git repositories, respectively, for anyone who wants one.

← Older revision		Revision as of 13:23, 10 February 2009
Line 1:		Line 1:
−	When you start out on a software project it is really important that you use some form of revision control for your code base. Even if you are the only developer on the project you will want to be able to roll back to previous versions of your software. As your project grows you'll want to involve more people, perhaps from other organizations, and being able to offer them a code repository to interact with is key.	+	When you start out on a software project it is really important that you use some form of revision control for your code base. Even if you are the only developer on the project you will want to be able to roll back to previous versions of your software, and to tag releases for production. As your project grows you'll want to involve more people, perhaps from other organizations, and being able to offer them a code repository to interact with is key.

−	There are lots of choices about what sort of revision control system to use. The key decision is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your ~~code,~~ into their own repository, and~~, where they can push back changes, or~~ make them otherwise available to you. While there are lots of options for both flavors, Subversion and Git are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub]	+	There are lots of choices about what sort of revision control system to use. The key decision you need to make is between centralized and decentralized repositories. Centralized revision control systems provide a single repository which people can check out, and check back in to. Decentralized repositories allow for more complex workflows where people branch your codde into their own repository, and make them otherwise available to you and others as needed.
		+
		+	While there are lots of options for both flavors, [http://subversion.tigris.org/ Subversion] and [http://git-scm.com/ Git] are currently the gold standard for centralized and decentralized revision control respectively. The good news is that if you would rather not run your own repository [http://code.google.com Google Code] and [http://github.com/ GitHub]