ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Bethard <steven.beth...@Colorado.EDU>
Subject Re: commit messages => JIRA
Date Fri, 24 May 2013 18:26:45 GMT
On May 24, 2013, at 12:21 PM, "Masanz, James J." <Masanz.James@mayo.edu> wrote:
> +10
> 
> Anyone have a reason for have a trigger anything beyond the simple rule of mentioning
CTAKES-#### in the commit comment 

The other rule that I use all the time on Google Code is that starting a commit message with
something like "Fixes CTAKES-190." closes the issue as fixed:

https://code.google.com/p/support/wiki/IssueTracker#Integration_with_version_control

An example of that in action:

https://code.google.com/p/cleartk/issues/detail?id=367

Steve

> 
> -----Original Message-----
> From: dev-return-1630-Masanz.James=mayo.edu@ctakes.apache.org [mailto:dev-return-1630-Masanz.James=mayo.edu@ctakes.apache.org]
On Behalf Of Steven Bethard
> Sent: Friday, May 24, 2013 12:55 PM
> To: ctakes-dev@incubator.apache.org
> Subject: commit messages => JIRA
> 
> We should consider asking infrastructure to enable this:
> 
> http://www.apache.org/dev/svngit2jira.html
> 
> Basically, it would mean that if you mention a JIRA issue in a commit, a link to that
commit is automatically added to the ticket. This is really nice for seeing exactly where
and how things get fixed.
> 
> Steve


Mime
View raw message