Git beats the pants off Subversion, so I am going to have to be another voice here backing it up. I’ll take Emacs + make + gcc + Git any day. I don’t yet have a preferred bug tracking system, though. Maybe ditz.

@Adam – I think that’s the same talk as Corey posted few comments above. Thanks anyway, it is an interesting vid. I love the cvs bashing lol

An interesting talk on Soure Control by Linus Torvalds

At work I have to use Telelogic’s Synergy (recently been bought by IBM). I hope it will be discontinued ;). It has good workflow ideas but terrible GUI and terrible CLI which tempts you to make big handling mistakes which an admin only can correct (not the user himself).
It has one very nice idea: you can not simply check out things, you need to create a “task” first with a description and a project tag, and then things you check-out stick to that task, and in the end you check-in the task. This makes for a really nice workflow in connection with a bug-tracker; i.e. you create a task to fix bug 75308, and you immediately see from the task contents what were the files you needed to touch.
As I said: nice workflow, but terrible implementation.

At home I use svn, and for my workgroup I had a brief look at Rational (just another IBM product …) but had not enough time to finish this evaluation.

For version control: svn, but soon switching for git,
bug tracking: trac,
and for development: eclipse with vim plugin ;)

FogBugz on Linux is PHP, so maybe don’t rule it out.

Wasabi is what the FogBugz folks use internally so that they can have the same codebase for ASP (for Windows) and PHP. They write it in Wasabi, run it through the “compiler”, and PHP comes out the other end for the Linux version, ASP for their Windows version. They ship the PHP, not the Wasabi.

I have developed a free open source bug tracking app which maybe you would NOT like, BugTracker.NET, because it only runs on Windows, but FogBugz was my biggest inspiration, so it might be worth a look for you.

@Nathan – well, I admit that I was never involved in projects of the size that would actually require more than svn. But yeah, I can see how it might be a problem as things scale.

@Corey – thanks for the video link. The cvs/svn bashing made me LOL.

I guess I need to look into git now. :P

Wow, trac is clearly the favorite here. I will need to check it out.

Bugzilla was written in Perl. FrogBugz was written in Wasabi (whatever the fuck that is). Trac is written in Python. I’m going with Python on this one.

Also, I’m not tracking bugs or doing source control with anything that has Microsoft in the name. I’m not paying out of my ass if I can have a free solution that is better. :)

@Ian – rub it in, why don’t ya? Lazy programmers use DH. One of those days I will get of my ass and move. You don’t even want to know when was the last time I upgraded my wordpres for precisely the same reason (laziness).

@Matt – actually, you probably should use a wild card there: “* is for people who are intimidated by emacs” :P

If there isn’t enough here to scratch your itch, I’ve put together a page of links to bug tracking discussions just like this one:
http://ifdefined.com/blog/post/2007/10/Links-to-other-comparisons-of-i ssue-trackers.aspx

Regarding source control, before you limit the list to cvs and svn, you might want to hear what Linus Torvalds has to say about “git”:
http://youtube.com/watch?v=4XpnKHJAok8

Use Borland StarTeam!

*shamelessly promotes own product*