Lan Barnes wrote:
On Sat, July 19, 2008 2:27 pm, SJS wrote:
--
Making more than one change at a time.
Stewart Stremler
Don't do that. Limit all changes in each commit to one issue in the issue
tracker. Reference it in your remark
If, while in a file, you spot another issue to change, enter a separate
ticket in the tracking data base and address it with a separate commit ...
after the tech lead has reviewed the issue and approved the work.
This prevents such jolly moments as breaking the build just before release
by cleaning up variable naming, or failing an audit because of changes to
code that are without reference or justification.
Do you have a list of "best practices" that you have accumulated over
the years? I'm lurking on these threads because I might have to start
using some of this stuff and would like to learn from someone who has
"been there, done that".
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
