I had a look at BZ46451. It suggests adding subversion properties to
enable the use of subversion bugtraq. This allows a better integration
of BZ into subversion commit messages and retrieval when looking at svn
logs.
There is a blog here
http://markphip.blogspot.com/2007/01/integrating-subversion-with-your-issue.html
and the spec is here:
http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt
(password guest).
The feature is optional, i.e. you don't have to use it. If you do use it
with subclipse or turtoisesvn it works as follows:
- the subversion clients allows to enter the bugzila id in a separate field
- it adds a final line to the commit message with a configured fixed
content plus inserted issue id (e.g. "BZ %BUGID%" leads to "BZ 45678"
when 45678 is provided as issue id during commit).
- since it knows the formatting of such messages, the client extracts
the id when showing svn log messages and provides links to the correct
BZ issue. The link URL is configurable, e.g.
https://issues.apache.org/bugzilla/show_bug.cgi?id=%BUGID%.
You can of course support the later feature even when not using the
above mentioned client by using the same formatting when providing a BZ
id in a log message.
Alternatively one can provide a regexp to extract the ID from a log
message. In this case you would provide the id still as part of the
usual log message, even when using subclipse or turtoise.
Multiple issues are always allowed, issue IDs will be separated by commas.
The implementation uses a few properties entered into subversion. The
client searches for the properties from the current working copy
directory up to the root of the working directory (not: the root of the
repository). So adding the properties only to the the trunk directories
should work fine.
There are open issues for viewvc and hudson to suppot the feature too,
but no advances on those feature requests in the last two years.
Nevertheless support from subclipse and turtoise might already make it
useful. At least I would find it useful :) similar to Mark's formatting
addition for svn revision URLs in Bugzilla.
Using it should be transparent, we don't loose anything becaue the info
is added to the svn log message in normal textual form. Of course if
nobody uses it, we don't gain much either. I actually expect the pattern
based feature to be more attractive, something like
\b[bB][zZ]\s*(\d+)\b
would already find a lot of issue numbers in the existing svn log
entries. There is an extended way one can use to be able to actually
find multiple numbers but the expression could evolve over time.
Comments?
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
