Keep a change log to describe all the changes made to program source files. The purpose of this is so that people investigating bugs in the future will know about the changes that might have introduced the bug. Often a new bug can be found by looking at what was recently changed. More importantly, change logs can help you eliminate conceptual inconsistencies between different parts of a program, by giving you a history of how the conflicting concepts arose and who they came from. Changelog Legend: ---- [+] = Added [*] = Changed [^] = Moved [=] = No Changes [x] = Deleted [!] = Bugs ---- (April 9, 2015) Version 1.0 Styled Themes Initial Release ---- (April 18, 2015) Version 1.0.1 Styled Themes [!] Font Enqueue Bug Fixed [!] Header Image Bug Fixed ---- (April 19, 2015) Version 1.0.2 Styled Themes [!] Theme URL Bug Fixed [!] Text-Domain Bug Fixed [!] Prefixing Bug Fixed ---- (May 4, 2015) Version 1.0.3 Styled Themes [!] Tags Bug Fixed [!] Text-Domain Bug Fixed [!] Prefixing Bug Fixed [!] Tgm Plugin Updated ---- (May 5, 2015) Version 1.0.4 Styled Themes [!] the_excerpt() function fixed. ---- (May 9, 2015) Version 1.0.5 Styled Themes [!] copyright default value in customizer fixed [!] jCarouselLite.js Bug Fixed ---- (May 22, 2015) Version 1.0.6 Styled Themes [+] Included License Information for all resources [!] Escaped all get_theme_mod [+] Add Unminified Version of Css and Js Used in the theme. ----