I asked two questions:
(1) suggesting a "multi-lock" model for Subversion -- this handled by
getting a better understanding of the upcoming locking enhancement and also
how to do read/write locking with a pre-commit hook script (sort of a
separate issue, as Ben pointed out). I'd still like to see a script of this
sort and if anyone wants to share one that would be great!
(2) suggesting that Subversion give more by way of user-commit-activity
metrics. This included a lot of thrashing about on my part trying to
explain the use case for what I wanted. The key parts of Ben's response to
this issue was as follows...
> From: Ben Collins-Sussman [mailto:firstname.lastname@example.org]
> > Bugtrackers will show info on closed tickets and
> > possibly progress towards closing, but not bytes-comitted
> > or number of commits per day, etc. These metrics coulkd be very
> > useful IMHO.
> And you can do them all with Subversion. That's why every project
> typically configures Subversion to send emails when people commit.
> That's why the 'svn log' command exists. That's why the 'svn diff'
> command exists. What other features do you need? I've not seen you
> mention anything yet that people don't already do with Subversion.
> >>> (That said, 'svn status -u' *will* show you which files
> have changed
> >>> in the server, so you can predict merges and conflicts before you
> >>> run 'svn update'.)
> > Yes, and if it also showed *how often* the files had changed, *how
> > much*,
> > and *by whom* (i.e. commit-activity by user) that would be even
> > better! ;-)
> People have written such scripts. It's easy to do. Just parse 'svn
> log' and 'svn diff' output from any client. Or write a post-commit
> hook that does the same statistics gathering on the server-side.
While I was looking for something different than what either, 'svn status',
'svn log' or 'svn diff' generates, I can accept that this finally answers my
second question, even if it simply says "this is something you can customize
Subversion to do, but not something the developers thought was important
enough or universal enough in usefulness to add to the application". Be
that as it may, I'd like to see those scripts. Again, if anybody has them
that they don't mind sharing, that would be fantastic!
I hope that if others are interested in tools for generating
user-commit-activity metrics from Subversion, that they will share their
interest with me and we can get a solid backbone of reliable scripts out
there to the community for all to use.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Feb 16 21:52:56 2005