Hi Simon, Agree with you, I am one such culprit for recently checking in codes for spring module refactoring without a JIRA. I realized the mistake later when I had to track the changes that were made for the entire spring refactoring work.
My suggestion is that, we should always have a JIRA associated for any code changes going forward and follow the "Fix TUSCANY-xxx" style of commmit comment. On Fri, May 29, 2009 at 10:06 PM, Simon Laws <simonsl...@googlemail.com>wrote: > I've noticed over the last couple of months that we have, on some > occasions, become a little lax about adding the "why" alongside the > "what" in our commit comments. Particularly problematic when there is > no JIRA to refer to. I'm as much a culprit as anyone else so I'm not > throwing rocks here but it would be useful to me if, as we're > reviewing each others changes, we can call out when we think the > comment isn't sufficient or clear enough so that the justification can > be updated and it becomes a matter of record. I seems that there are > some innovative discussions firing up on 2.x and it would be good to > be able to help people follow the twists and turns as best we can. > > Is this a fair observation? > > Simon > -- Thanks & Regards, Ramkumar Ramalingam
