manage concurrent development (was: email settings for sending mail on checkin of files,)

[daniel . kabs]

Aaron Bono wrote:
> May I ask what you are doing with this email?  I can't think of a
> reason to myself and am very interested in new and innovative ways
> people manage concurrent development.

Well, I just configured "loginfo" to this effect and I find it useful to 
have CVS mail a message to certain developers when a new revision of a 
file is committed.

I think it gives a nice overview of who commits what. Running a nifty 
mail reader you can also do all kind of interesting search queries (for 
users, files, commit message,...). It's also a kind of active (push) 
service e.g. when someone is waiting for a certain fix to be commited.

What I don't like about "loginfo" is that it does not group commit 
emails but sends one per directory.

I like to know what alternatives exist that help to keep an eye on 
commits and how to track grouped changes. What do you recommend?
Something like Mozilla's Tinderbox?

Cheers
Daniel Kabs