Some projects teams throw a small office party for major releases - so why not for 1000th commit? 1000th commit is a good marker, usually project has progressed quite nicely by that time.
Do you celebrate or give any extra attention to such 'magic number' commits?
Too easy to game. You get up around 950 and you'll start seeing trivial and/or bad commits just to get the party. A milestone release at least implies you passed QA first.
Of course! Our section has a number, each time a repository reaches that number a mail is sent with the log + diff of that commit, some statistics (LOCs per coder etc) and a few anecdotes...
We make a celebration when completing certain testing stages or development stages for large projects. Usually the choice of stage is based on the bottleneck. When you pass that, we throw a party, and when we deploy to production, another party.
I considered it something of a milestone when the revision number on a project I worked on last year hit 2008, no party though.
Every commit after that felt like we were heading boldly into the future.
Dumb and geeky I know.
Here's a twist, throw a party but the dev who makes the 1000 commit has to buy the beer
I agree with the comments on gaming the system. You don't really want people committing like crazy just to have a party.
It seems the real problem is you feel your team is not socializing enough. Why not schedule regular socials / mini-parties / poker nights / whatever, and then have your big bash when the release happens.
We had a race to reach the 10,000th bug in bugzilla. The QA guys went into overdrive it was great.
Luckilly it the 10,000th bug wasn't in the product I was workign on...
I think magic number goals can be quite motivating, I think we've noticed the 1,00th and 2,000th comit, but nothing special came of it.
We generally celebrate (?) the number of bugs. The guy who raised bug 10,000 bought cakes. So did the ones who raised 11k and 12k.
We've not got to 13,000 bugs yet, but we're finding more all the time :)