[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is a ChangeLog file realistic if /lots/ of developers adding /lots/
Re: Is a ChangeLog file realistic if /lots/ of developers adding /lots/ of changes?
19 Jun 2003 12:04:53 -0400
If you have any advice or ways to streamline the process I would very
much like to hear it.
spend one hour a week as a group reading change logs (and only change
logs -- no code!) for the week preceding. discuss applicability of
changes, especially whether or not the change introduces new problems.
note change/changeback pairs. characterize and categorize changes to
determine if a larger-scope redesign is indicated (or rather, soon to be
over time, this will streamline things because your group will be able
to recognize useless (or less than optimal) changes that should never
have been made in the first place, and thus reduce that kind of noise.
you might also develop ability to pre-emptively figure out more direct
and more robust changes to make.
basically, to understand the code is one thing, to understand how you
change your code is the next best thing, and to understand how you
understand how you change your code is the best thing. change logs can
help you do this.