geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <>
Subject Re: Let us please use a JIRA for every code change we make
Date Tue, 19 Sep 2006 03:01:40 GMT

On Sep 18, 2006, at 1:43 PM, Jason Dillon wrote:

> I think it is a bad idea to force every change to have a JIRA issue  
> created (or associated).  This will only lead to forcing people to  
> add a bunch of junk to JIRA.
> -1 to forcing each change to have a JIRA... common sense should  
> dictate which changes need JIRA issues and which do not.
> JIRA is more useful to track high-level coarse grained information  
> and bugs fixed.  If you need fine grained history, look at subversion.

That pretty much reflects my sentiments.  I usually file JIRAs for  
anywhere from 50% to 80% of the commits I do.  Occasionally, I've  
filed jiras after the fact as sometimes I'll check something in and  
think, "that might be something for the release notes, I should file  
a jira."

I'd say a good system is if you see a commit that should have a jira  
for the release notes, poke the committer and encourage them to add one.


> --jason
> On Sep 18, 2006, at 11:03 AM, Prasad Kashyap wrote:
>> As we move back towards CTR, can we please adopt the practice of  
>> using
>> a JIRA for every code change we make, however small the code change
>> may be.
>> Since we have assumed the responsibility of providing good
>> documentation/discussion with all code changes, a JIRA provides that
>> crucial link between a particular change and it's open discussion.
>> Some use the JIRA comments for discussion. JIRA comments are good
>> enough for small minor changes. For most others, it is the dev-list.
>> If the discussion is held on the dev-list, the JIRA should mention  
>> the
>> link to that discussion's archive page. Use your favorite archive
>> site.
>> And then, as you commit the changes, please mention the appropriate
>> JIRA under which the code was being changed.
>> For posterity sake, this will ensure that a link to the discussion is
>> is always available for any change that went into the file.
>> Please feel free to correct, modify or suggest better methods to  
>> keep this link.
>> Thanx
>> Prasad

View raw message