pouët.net

we use a very simple, but relatively efficient bugtracker called "phpBugTracker"
it's good enough i guess..

I get what the advantages are, the question is more if they outweigh all the overhead of dealing with a complex management system, as opposed to just emailing a few source files around. Also doesn't the rigidity of any sort of management software (or even just strategy) get in the way of productivity if you're doing something like, say, a demo? And doesn't it get boring?

svn everywhere, even for 4k

At work we use at least two bugtracking system + one versionning system. On top of that I'm using another versioning system (git) to manage / merge my own branches.

As for home, CVS does the job. SVN sounds like an over-engineered cvs, without being lightweight so I said fuck to that long ago. I guess I'll switch to git at some point.

at work, svn|cvs + a bug tracker + an issue tracker for some teams
at home, nothing but seriously considering svn

SVN in demos and work. And in work we use JIRA.

Influence Device: once you did a project of whatever kind with more than one person (yourself) involved, you will realize that the idea of "mailing the source files will do it" is doomed to fail. we did it once at university and that was the very last time. the use of management software (by which I mean: more than SVN or something like that) may be overkill for a demo, but even there it might help.
and concerning that "get in the way of productivity". again, may be true for demos as you are usually limited with your schedule and more importantly free time, so it might not help here.
for bigger projects some sort of manegement is pretty necessary IMHO.

The nightmare of 3 coders and no svn at the last three breakpoints has been quite tormenting... nowadays it feels having svn is pretty much necessary to get anything done also demowise.

plus you can write funny commit comments ;)

rarefluid: that's the best part, yeah :)

source depot and product studio at work (source depot is -epic-)

cvs and a wiki page for demostuffs

bugzilla @ work

svn at work, "just gimme a .lib and a .h" for demostuff.

svn1click prepares subversion for use (or shortly ;) deploy) on windows for local use. nifty if you want to take a small peek or save yourself from all the work. it has stuck at some subversion version but i really couldn't mind less as it has done the job quite well so far.

svn, fogbugz and pmwiki.

anes: thanks!

perforce / proprietary bug database at work
svn at home (yes, for my 68k code :))

StreberPM created by Pixtur, both at work and for demos.

sourcesafe at work for versions. bug tracking and version control for demos...?? What are you speaking about??

version control for demos is great, you can experiment crazy things when you smoked too much eucalyptus without fucking up your demo =)

i'm using VS2005 and SVN (with sourceforge:) for demoing and job, but:

- for the 4 amigaoses (classic,os4,mos,aros) and for dreamcast, I use a AMIDEVCPP version of DEVCPP, re-patched with a DC devkit, the whole things using differents GCC or mingwin installations (devcpp is more or less a free clone of VS6 ). Maybe i'll do some eclipse/CDT configurations for my projects by pure vice.

- I used to be a fan of Stormc4 on amiga os3.9 (compiling 680x0/ppc), which was incredibly good for an amiga IDE released in 2000 (excelent debugger and compiler), and unknown to the amiga devs :( (stormC3 was a shit)

mercurial at work, cvs for demos

perforce at work. should be perforce for demos, but our server went down ages ago and we never got around to putting it up again. :)

once there's a good windows port of git i'll probably try convert mfx to use it. little less reason for "gaah no intarweb! we're all gonna die" stuff.

216 -- I'm using a win32 port.. what is missing from it?