Go to bottom

[serious thread] are you using any bug tracking / project management / version control software ?

category: general [glöplog]
like bugzilla, JIRA, perforce, subversion, etc... or homemade system ?

at work or even for your demos ?

i've always been wondering if a simple notepad or excel sheet aren't enough for many cases, especially when teamwork is limited :>
added on the 2007-09-13 17:54:50 by Zest Zest
we use svn.
added on the 2007-09-13 17:58:00 by rmeht rmeht
trac + subversion for my personal use
Axosoft is a good one. VS integration, web and window client. It's free for one person. Todo List for notes and simpler things
added on the 2007-09-13 18:21:36 by Xetick Xetick
svn here too
added on the 2007-09-13 18:27:29 by hcdlt hcdlt
CVS, but we want to switch to subversion soonish.
added on the 2007-09-13 18:47:24 by raer raer
bazaar isn't that bad too. very easy to use, especially with local repositories. Frontends lacked when i tested it though...
added on the 2007-09-13 18:48:30 by raer raer
svn at work and for demos.
added on the 2007-09-13 19:09:20 by uncle-x uncle-x
svn, both for work and demos.

we also have mantis configured and running, but don't really use it :)
added on the 2007-09-13 19:13:14 by ryg ryg
Trac + svn. Work & personal & demo work.
added on the 2007-09-13 19:56:51 by Preacher Preacher
svn+trac at home, svn+mantis+sharepoint (blegh, ms bloat) at work
added on the 2007-09-13 19:58:26 by glow glow
Is it really worth it?
added on the 2007-09-13 20:29:13 by doomdoom doomdoom
(I ask cause I'm curious, trolling doesn't start for another 3 hours)
added on the 2007-09-13 20:29:44 by doomdoom doomdoom
added on the 2007-09-13 20:41:03 by apricot apricot
yes, I am subject to all of these systems at work. Thank God I'm only affected by CVS at home :)
zest, many software houses make the mistake that a simple spreadsheet for managing bugs, issues, change proposals and requirements is sufficient. but it really isn't.
Influence Device > SVN for example is the ultimate tool for lazy coder, if you don't remember what you've done before, it'll remember it for you. If you screw somewhere, it doesn't matter you can revert back to where you were.

It's also a sort of security, backup are less needed (also backing-up repository should be done on a regular basis). And ultimately in team work, it avoid you the error-prone synching operation.

(and i'm not talking about the use of commit's message to keep track of changes at a global level or bug-resolving with track).

One advantage of SVN is that he is small enough to be let in background of any computer (for mono-coder project), so yes it's really worth it
added on the 2007-09-13 21:04:26 by Twinside Twinside
bzr is great if you code on a laptop which isn't connected at all times. svn/cvs need a central server.
added on the 2007-09-13 21:04:34 by sang-soo sang-soo
warpr: yes for that it is really good!
'bout CVS. I think svn is much better 'cause you don't need to handle versions on a per-file basis as with CVS... but tell that to my boss ;)
added on the 2007-09-13 21:11:55 by raer raer
svn, previously cvs, but that was years ago, we were pretty fast in adopting svn
added on the 2007-09-13 21:14:28 by thec thec
Perforce at work.

I'm not too fond of Jira although it can prove useful to keep track of bugs and to assign them to code slaves :)
added on the 2007-09-13 21:15:49 by keops keops
svn + buildbot + bugzilla at work, svn + buildbot at home.
added on the 2007-09-13 21:32:26 by kusma kusma
warp: svk is also nice for distributed repos, since it works well with an svn-based workflow.
added on the 2007-09-13 21:33:26 by kusma kusma


Go to top