Submitting Code Changes

Version 1 by farshid
on Aug 04, 2012 21:37.

compared with
Current by farshid
on Aug 04, 2012 21:41.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History

h3. Why do we need this?
As we are growing, understanding the changes that went into a specific DP, or release gets increasingly hard. The QE, PM, documentation and SDK teams all need to make sure we understand exactly what exactly has been changed.

Commit messages alone are a poor tool for this. Major changes often have very many commits and for people outside of the component, it is often impossible to tell whether a specific commit is part of a specific feature or bug fix. Therefore we need to have a simpler way to reduce the information and understand what was addressed in a build.