C> On Sun, Jan 16, 2011 at 7:16 PM, Happy-melon <happy-melon(a)live.com> wrote:
> Isn't that what release notes are for?
Say, how do you pros see what changed?
Here is my extra stupid way. I do it every few weeks.
cp RELEASE-NOTES /tmp
svn update
diff --ignore-space-change -U0 /tmp RELEASE-NOTES
Often old lines are shown again, because somebody tidied their
formatting. A svn diff wouldn't be any better.
The worst thing is each 1.17 to 1.18, 1.18 to 1.19 change, when the
whole file changes.
So how do you folks track RELEASE-NOTES level changes (not source code
level changes, too many), coinciding with your SVN updates?