Hi all,<div><br></div><div>Nick's going to think this is directed at him since he just committed, but it's not; I've been observing this for a while now. :)</div><div><br></div><div>Would committers please do everyone else a favour and include at least *one line* of description about the included change? The common pattern at the moment seems to be to put the issue number in the commit message and the package information in the issue, but this gives no clue what was done to fix the issue. Particularly now that diffs in the emails are turned off, this makes it basically impossible to follow what's going on without loading every committed package and looking at the code.</div>
<div><br></div><div>A simple indication of what class/method you changed/added/deleted would be a start. For example:</div><div><br></div><div>----------</div><div>Fixed <a href="http://code.google.com/p/seaside/issues/detail?id=xxx">http://code.google.com/p/seaside/issues/detail?id=xxx</a></div>
<div>Added WAFoo>>bar, which wraps the call to super in an exception handler</div><div>----------</div><div><br></div><div>Ideally, if it's not obvious, you'd also include a line or two about the reason you made the fix you did.</div>
<div><br></div><div>This should only take you a few seconds and I (along with anyone looking back at the code history in the future) will thank you.</div><div><br></div><div>Thank you! (see? :) )</div><div><br></div><div>
Julian</div>