Lost Changes
Lost changes are a nuisance and a waste of time. The main cause of lost changes is incorrectly merging release candidate changes with released code. This is usually because a conflicting edit was not recognized, or the programmer incorrectly merged the two sets of changes.
The solution to this problem has three parts. The first two parts of the solution are always start with all of the released code and always release changes frequently. Frequent releases minimize the chance that the released code has changed. When changes do have to be merged, frequent releases minimize the impact. Remember Continuous Integration.
The third part of the solution is your Unit Tests. Code can't stay lost for long if there's a test somewhere relying ...
Get Extreme Programming Installed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
