standards: Change Logs

1 
1 6.8 Change Logs
1 ===============
1 
1 Keep a change log to describe all the changes made to program source
1 files.  The purpose of this is so that people investigating bugs in the
1 future will know about the changes that might have introduced the bug.
1 Often a new bug can be found by looking at what was recently changed.
1 More importantly, change logs can help you eliminate conceptual
1 inconsistencies between different parts of a program, by giving you a
1 history of how the conflicting concepts arose and who they came from.
1 

Menu

1 
· Change Log Concepts
· Style of Change Logs
· Simple Changes
· Conditional Changes
· Indicating the Part Changed
1