Stop me if you've heard this one before...
Currently we're tracking code changes back to a defect/ticket/bug number
by putting the defect number in the commit message.
Unfortunately, searching the commit messages for defect numbers is
grossly inefficient since it's not an indexed field. As the repository
gets bigger, the search will become slower. (Because of peg branches,
merging, and copying, you have to search the entire repository to ensure
a 100% accurate lookup.)
Wouldn't it be spiffy if Subversion had an indexed revision property?
This would enable better integration with a change management tool by
allowing a commit/revision to be tied to a defect/ticket/bug number with
Currently, it is quite slow to pull such basic information as:
-finding all commits/revisions for a defect
-finding all files associated with a defect
-verifying that a defect isn't being moved across releases (if
you checked into release 1.0 with defect 123, you shouldn't be able to
re-associate defect 123 to release 2.0.)
-what defects are in a baseline (range of revisions.)
Speed also limits the amount of idiot checking you can do, since you
cannot get the information in real time. (Making the user wait 30-90+
seconds while you parse log messages for defect numbers isn't going to
Granted, we could set up our own database and have the commit hooks to
write this information to it, but it's extra work, it seems redundent
(svn is a database after all,) you have to keep the defect number in the
commit messages in sync with the database, and let's be honest, a
version control system without a change management system is a random
It would also be peachy to have a 'svn commit -bug_ids BUG1[,BUGn]'
argument to automatically update a standard svn:bug_id indexed property.
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. 117
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jul 17 18:04:48 2006