db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Discussions in and out of Jira (was Re: Feature list for adding JMX extensions to derby)
Date Thu, 08 Jun 2006 19:11:38 GMT
David Van Couvering wrote:
> No, you understood me, and I see what you are saying too.  I guess it's
> a question of making it easy to find out what's going on around a
> particular feature.  I guess you x-ref to a mail thread?
> I guess I don't have a *strong* preference, I just thought this kind of
> thing is easier to track if it's in the JIRA database.  Since JIRA
> entries get copied to the dev list I didn't see how it made much
> difference in terms of it being available for all to see.  Or is that
> not true?

A lot of people don't look at the Jira activity because it's so high.
Another problem with the whole discussion being in Jira is there's no
way to remove incorrect information, which is inconvenient because it's
something of an audit repo for the issue.

Actually, I really like what I've seen Mamta and Halley do lately. I've
noticed they have both been posting a subject that references the Jira
issue, but keeps the actual discussion on the development list.

Here are examples:

Subject = "[Derby-655] : getImportedKeys returns duplicate rows in some

Subject = "DERBY-1376 - Text for exceptions - File



> David
> Jean T. Anderson wrote:
>> David Van Couvering wrote:
>>> A note that it would be great if these discussions could be maintained
>>> as comments on the JIRA.
>> Actually, do we want to maintain discussions in Jira?
>> On other apache lists, I consistently see posts that chase development
>> discussions *off* Jira and back onto the development list. It's great to
>> include links to the discussion in Jira, but otherwise summarize the
>> info.
>> or perhaps I misunderstood what you meant?
>>  -jean
>> <snipped>

View raw message