On Sun, Apr 13, 2014 at 10:01 PM, Karl Tomlinson <mozn...@karlt.net> wrote: > Very often I've found that the intended approach changes during the > life of a bug, and there is no clear summary in the bug of what > eventually was done. It is then necessary to go back through > multiple revisions of the patch and associated comments and > replies to find out the reasoning. Add in the complexity of > multiple changes in one bug, and having a single summary in one > place would be very helpful, and is, when it is there.
Indeed, putting the rationale in the commit message helps ensure what gets pushed is what gets explained, by removing one level of indirection. But if people aren't writing good Bugzilla comments now, they're probably not going to write good commit messages either. So we need to both make it easier and enforce it more consistently through the review process. Gavin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
