2014:version_control_-_patterns_and_practices
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2014:version_control_-_patterns_and_practices [2013/10/29 13:34] – created jonjagger | 2014:version_control_-_patterns_and_practices [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| \\ | \\ | ||
| This session takes a walk through the software development lifecycle and examines the | This session takes a walk through the software development lifecycle and examines the | ||
| - | role the source control system plays – what we store, why we store it, how we change it | + | role the source control system plays - what we store, why we store it, how we change it |
| - | and then later how we reconstruct what was changed and why. We’ll look at the various | + | and then later how we reconstruct what was changed and why. We'll look at the various |
| forces that dictate our branching (and subsequent merging) strategies along with some | forces that dictate our branching (and subsequent merging) strategies along with some | ||
| of the less contentious policies we can adopt to ensure our system continues to evolve | of the less contentious policies we can adopt to ensure our system continues to evolve | ||
| Line 23: | Line 23: | ||
| preserving history across file/folder moves and renames is just one aspect where tool | preserving history across file/folder moves and renames is just one aspect where tool | ||
| specific knowledge matters. But before we can get there we need to deal with their lack | specific knowledge matters. But before we can get there we need to deal with their lack | ||
| - | of agreement on a common vernacular…\\ | + | of agreement on a common vernacular. . .\\ |
| \\ | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
2014/version_control_-_patterns_and_practices.1383053649.txt.gz · Last modified: 2016/06/11 14:05 (external edit)