Difference between revisions of "Version Control"
m (correct typo) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Version Control is sometimes internal to a software application or tool. Users of | + | Version Control is sometimes internal to a software application or tool. Users of LibreOffice Writer will be familiar with how you can open a document sent by a colleague, turn on "track changes" and then your edits to the document will be clearly shown so that you can send the document back to the original author to provide feedback and the opportunity to merge changes in a friendly, efficient manner. |
Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, [[Subversion]], Mercurial and Git or others. | Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, [[Subversion]], Mercurial and Git or others. | ||
For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git. | For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git. | ||
| + | # [[Subversion/Vendor Sources]] | ||
| + | # [[Git/Vendor Sources]] | ||
== Illustration of Version Control Services== | == Illustration of Version Control Services== | ||
| Line 12: | Line 14: | ||
== See Also == | == See Also == | ||
[[Version control]] | [[Version control]] | ||
| − | |||
| − | |||
| − | |||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:Subversion]] | [[Category:Subversion]] | ||
[[Category:Version Control]] | [[Category:Version Control]] | ||
Latest revision as of 21:48, 13 May 2013
Version Control is sometimes internal to a software application or tool. Users of LibreOffice Writer will be familiar with how you can open a document sent by a colleague, turn on "track changes" and then your edits to the document will be clearly shown so that you can send the document back to the original author to provide feedback and the opportunity to merge changes in a friendly, efficient manner.
Version Control in a software development environment is a large part of the infrastructure that makes software development possible -- because it provides the same feedback and opportunity to merge changes in a friendly, efficient manner. The tools that software developers use are CVS, Subversion, Mercurial and Git or others.
For distributed version control, merging and merge tracking including incorporation of "Third-party code" into your software products is really difficult or impossible with Subversion yet possible and even fun with Git.
Illustration of Version Control Services[edit | edit source]
This illustrates how infrastructure can be created to provide version control systems, viewers, access control mechanisms with various version control backends to a group.
<mm>flash</mm>
