geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Is JIRA for sandbox'ed and branch'ed code? (was Re: [jira] Created: (GERONIMO-2407) openwire impl in gcache won't compile)
Date Tue, 19 Sep 2006 16:40:46 GMT

On Sep 18, 2006, at 10:59 PM, Jacek Laskowski wrote:

> On 9/15/06, David Jencks <> wrote:
>> Jacek,
>> This use seems completely appropriate to me..... Bill is supplying a
>> patch against some code that he cant commit against himself.  Where
>> else could he put the patch?  Among other advantages, using jira
>> gives him the opportunity to explicitly authorize apache (or the
>> geronimo committers) to apply the patch... if he used the mailing
>> list it would not be so clear IMO.
> Whenever I think about our tools we can use to help in development
> process I try to see their final results. In this case - would it ever
> become part of RELEASE NOTES that's generated from JIRA? It would not
> if gcache never did its way to the trunk, would it? I think JIRA is
> not meant for sandbox'ed code. JIRA messages may mislead easily that
> gcache is already on trunk. On the other hand, it bothers me that we
> can't provide anything better to help non-committers contribute to it.

Not having tried to write release notes :-) I'm not sure what  
problems show up, but certainly not everything in JIRA goes into  
every release notes: the issues have to be filtered by branches/ 
version.  So as long as JIRAs for sandbox stuff don't have a release  
version number associated with them they shouldn't get into any  
release notes.  Maybe along with "Wish List" we should have "Sandbox"?

david jencks
> I'm not convinced with JIRA and gcache playing together, but don't
> have anything better to advocate. Eh, I'll have to get used to it.
> Jacek
> -- 
> Jacek Laskowski

View raw message