[Geoprisma-dev] Project management / Pointers for potential contributors (doc)

[Daniel Morissette]

Yves Moisan wrote:
> 
> Right.  So that means either to have a ticket created first then that
> ticket url is used in the commit message or, if the change is not worth
> opening up a ticket, make sure the commit comments are verbose enough.
> 

BTW, no need for the full URL in the SVN log message. With Trac/SVN 
integration, you can just put "#123" in the SVN log message and that 
will automatically link to the ticket number when you look at the change 
log in Trac.

You can also use the notation "r1234" to refer to a SVN revision number 
in a Trac ticket comment (or in Trac wiki) and that will automatically 
link to the changeset (svn diff) when you click the link.

Here is an example of this notation in action, a ticket referring to a 
changeset (look for r9388 in the last comment):

http://trac.osgeo.org/mapserver/ticket/3129#comment:2

And the corresponding changeset refers back to the ticket in its change 
comment (look for #3129):

http://trac.osgeo.org/mapserver/changeset/9388

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/