Ramkumar R wrote:
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.
--
Thanks & Regards,
Ramkumar Ramalingam
Folks,
I have to admit to NOT raising a JIRA for "trivial" changes - instead I try to put the explanation
into the Commit message.
The sort of change that I regard as too trivial for a JIRA are upgrades to error messages which are
not changing any significant logic in the code.
If people feel a need for a JIRA for everything, then I'll consider changing, but I'd prefer to keep
the burden low for doing minor incremental improvements of this kind.
Yours, Mike.
