On Wed, Jun 3, 2009 at 8:16 AM, Mike Edwards <[email protected]> wrote: > I have to admit to NOT raising a JIRA for "trivial" changes - instead I try > to put the explanation into the Commit message. >
+1 > 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. > Creating a jira for each single commit will flood the dev list with unnecessary jira notifications (create, close, etc) and will probably make users that are lurking in the dev list to unsubscribe... It should be pretty simple to just add a simple description on the commit log message, and associate it with a jira if one exists. This makes life easy for the ones just looking into the commit e-mails from last night, or the ones looking into some tool like TortoiseSVN, but also simple for people browsing jira, as the commit tab will easily display the list of revisions that were changed in relation to this specific jira. -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
