[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Appropriate use of revision properties?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-01-11 18:57:06 CET

One of the (many) things we want to track with our usage of Subversion
is not only who changed what and when, but for what internal
change-tracking ticket #. I realize that there are issue tracking
systems that integrate with svn, but that's not really an option here.
 I'm envisioning the following workflow:

Issue is logged in ticket system & assigned ticket #1234
Issue is assiged to developer
Developer makes requisite changes
Developer sets a rev prop called "Ticket" and sets a value of "1234"
Developer commits change to svn

Yes, I could use branches or tags, but this may make bundling fixes
for a number of tickets into one release cumbersome (with or without
merging every time).

My thinking is that by doing this, we can more easily query subversion
logs later to determine what changes were made for ticket 1234. The
alternate would be to have a standard commit message format and
require everyone to use it; however, that would require parsing every
commit message to find the ticket number I'm looking for.

Where would I find this revprop reported later? I'm currently using a
tweaked svn2cl (originally written by Arthur de Jong) to generate an
HTML changelog from the output of svn log --xml --verbose - will
revprops be included in that output?

Am I way off course here? How do other developers/teams manage
tracking like this?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 11 19:03:43 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.