Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
Date: Mon, 20 Nov 2006 11:49:24 +0100
From: Vemund Ostgaard <Vemund.Ostgaard@Sun.COM>
Subject: Re: Issues that are fixed in trunk  and needs to be reviewed for
 porting to 10.2 branch
In-reply-to: <45615245.9020907@gmail.com>
Sender: Vemund.Ostgaard@Sun.COM
To: derby-dev@db.apache.org
Message-id: <45618834.9010000@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <45615245.9020907@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7.12) Gecko/20050927

Rajesh Kartha wrote:

> Hello,
>
> I am yet to find a simple way in JIRA to review the list of  issues 
> which are fixed in trunk and could be ported to
> branches.
>
> Anyways, I wrote a simple utility to dump all the DERBY related JIRA 
> data into a database and enable me to
> run SQL queries.
> (If the community thinks such a utility might be useful for Derby, I 
> am more than happy to contribute that).

+1

I think that could be useful for Derby if we want to implement some 
metrics based on the information in Jira for instance.

Vemund