db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: Tagging bugs - Re: [jira] Commented: (DERBY-2024) Remove JUnit utility method JDBC.vmSupportsJDBC2
Date Thu, 02 Nov 2006 17:17:45 GMT
On 11/2/06, Daniel John Debrunner <djd@apache.org> wrote:
> Andrew McIntyre (JIRA) wrote:
> >     [ http://issues.apache.org/jira/browse/DERBY-2024?page=comments#action_12446453
> >
> > Andrew McIntyre commented on DERBY-2024:
> > ----------------------------------------
> >
> >
> > I've been marking bugs with that tag in comments to make it easy to query JIRA for
tasks related to removing JDK 1.3.1 support. I'll be glad to continue that habit if others
find it useful.
> Is this any better than the existing mechanism where they are all a
> sub-task of  DERBY-1982?

Well, it does allow tagging bugs that aren't directly related to
removing JDK 1.3 support, but where the solution for the bug required
use of a 1.3-specific API that has a better alternative API to use in
1.4, or where some undesirable concession was made to accommodate 1.3
behavior. See, e.g. http://issues.apache.org/jira/browse/DERBY-1462,
where additional (undesirable) sedding was added to remove warnings
that only occurred on 1.3. I had another example but can't find it
because JIRA is being cranky right now.

> It is an interesting approach though because I've been wondering how to
> tag a bug as being in a certain category without having to add new Jira
> fields. For example all bugs that cause incorrect data to be returned to
> the application.
> Now seeing your tagging I see it could be done that way or I could enter
> a Jira issue of type Task and just link relevant bugs to it.

I think the tags are nice for this purpose because it's a
cross-cutting concern that doesn't fit squarely into the component /
issue type scheme. But really, either way works. I like the tagging
method because I can pull up JIRA and put 'Derby JDK13CLEANUP' into
the search box and get all the related issues quickly. Just as quick,
I suppose, to have everything linked / subtasked off of one issue and
bookmark that.


View raw message