Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Mime-Version: 1.0 (Apple Message framework v730)
In-Reply-To: <42A076B9.5090603@debrunners.com>
References: <429DE714.8030207@sun.com> <429DEBC4.4080307@sun.com>
 <429DFB5B.1000801@debrunners.com> <429E0502.30609@sun.com>
 <42A076B9.5090603@debrunners.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <236F3C8E-0026-4D71-A99B-A7F906710A56@gmail.com>
Content-Transfer-Encoding: 7bit
From: Andrew McIntyre <mcintyre.a@gmail.com>
Subject: Re: Proposed JIRA workflow changes
Date: Fri, 3 Jun 2005 09:31:31 -0700
To: "Derby Development" <derby-dev@db.apache.org>


On Jun 3, 2005, at 8:26 AM, Daniel John Debrunner wrote:

> This is a posting from the general incubator list, it includes a
> reference to the fact that Jira can be linked to SVN to perform patch
> tracking.
>
> No idea how to do this, but other Apache projects are doing it (see  
> the
> jira link below) so it might be useful for Derby.
>
> Dan.

If we'd like this feature enabled for Derby, and I would, it looks  
like we'll have to request the JIRA admins on infrastructure add us  
to the list of projects that are indexed by the JIRA subversion  
plugin. I have another JIRA-related request to make over at infra, so  
I'll go ahead and ask for this as well. The plugin scans the  
subversion logs for a project and links any checkins with a JIRA ID  
back to the JIRA entry itself on the 'Subversion commits' tab, so all  
that needs to be done is to have it enabled.

andrew