[GeoNetwork-devel] Closing trac tickets and git commits

GeoNetwork GeoNetwork Developer
1

Hi,

i'm subscribed to geonetwork-devel to closely follow GN development, and since we're receiving the messages sent by all trac issues, i wonder if it'd be possible for commiters fixing/closing issues to reference the github commit in a comment when closing trac issues ? That'll ease cross-referencing between git and trac.

Atm, the messages we get only contain:

   * status: new => closed
   * resolution: => fixed

which is not really helpful when one wants to know how the issue was fixed, by what commit. Sure, i can git log on the repo and look for the issue number, but wouldnt it be simpler to directly reference the github commit in trac ? I think this was done i the past when referencing svn revisions, and this is a common practice in most open-source projects.

What do you devs think about it ?
--
Landry Breuil

2

Breui,

I have seen a few of these tickets - in general, you can still locate the
commit by searching the commit logs for the ticket # or title.

In my opinion I find lately, in general, the committer do put the github
commit code. On occasion it is misses (they/we are human ). When you notice
such a thing, I suggest that you reply asking for the github commit code or
better yet, if you have time, you can locate the commit and add the comment.

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/Closing-trac-tickets-and-git-commits-tp5004540p5004646.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.