Slashdot Mirror


Ask Slashdot: How Do You Track Bugs For Personal Software Projects?

An anonymous reader writes "One of my personal software projects grows bigger than I thought and the bugs becomes too many to just remember. I looked around for an open source bugs tracking system but found no ideal solutions. Ideally I wanted a simple system that does not need server setup and extra database setup, and can run under Mac OS X. Another option is a cloud service if it's affordable enough. Any suggestions from Slashdot?"

15 of 221 comments (clear)

  1. Mantis by Anonymous Coward · · Score: 5, Informative

    Been using Mantis for years, easy to install, easy to setup, easy to manage.

    1. Re:Mantis by cicatrix1 · · Score: 3, Informative
      --

      I know more than you drink.
  2. Lighthouse by Literaphile · · Score: 4, Informative

    They have a free plan - http://lighthouseapp.com/

  3. Use unfuddle.com by Drake42 · · Score: 4, Informative

    I am not associated with them, nor employed by them. But I've used them for many projects now and been generally happy with the result.

  4. JIRA by rveldpau · · Score: 3, Informative

    How about JIRA? Used by Enterprises all over the place. You can get it OnDemand from Atlassian for $10 (which is actually just a donation to Room to Read). Check out http://www.atlassian.com/software/jira/overview

    1. Re:JIRA by Anonymous Coward · · Score: 0, Informative

      I'd avoid Atlassian. When I asked them for screenshots to show to my boss, they called me a "stupid petulent(sic) child." They then went on a rant about how much better San Francisco is than Seattle(my domain name has seattle in it). Other than my experience with calling Microsoft about a volume license, they were the most unprofessional company I have ever dealt with.

  5. Redmine by Roadmaster · · Score: 4, Informative

    When I need to set up a self-hosted project and bug tracker, I normally use Redmine, which is very easy to use. It's written with Ruby on Rails, and so should be relatively easy to get a local SQLite-backed copy running on Mac OS using Rails' built-in mini web server.

    This post is overly complicated but some of its information may be useful:

    http://www.redmine.org/boards/2/topics/2768

  6. Fossil is the way to go. by Noryungi · · Score: 5, Informative

    Fossil (http://www.fossil-scm.org) is just great: it allows you to manage your code, documentation (wiki) and tickets (bugs).

    It's really small and lightweight, offers its own web interface and can be made to run on a central server with a CGI script. Oh, and it's free and open-source.

    It also scales very well: for instance the entire NetBSD code base has fossil repositories.

    I am currently re-starting some personal projects and I will be using fossil almost exclusively for these. It's simply fantastic.

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
  7. Fog Bugz by mgreider · · Score: 3, Informative

    We use https://www.fogbugz.com/ and have been happy with it. It has more features than you'll need to a small project. They have free versions for single users.

    --
    -- Best Greetings Cards Ever :: www.sm-mancards.com
  8. Fix them by SeanBlader · · Score: 1, Informative

    I tend to fix a bug as soon as I find it. That solves the problem of tracking them.

    1. Re:Fix them by RustNeverSleeps · · Score: 3, Informative

      This is fine for small, truly personal projects, but once you have a product with other users (as I do), you end up having to prioritize bug fixes. You simply can't fix every single bug right when it's reported. Bug trackers are also good for keeping track of new features to be added in the future, refactoring you'd like to do, etc.

  9. Re:highlighted comments in source by 19thNervousBreakdown · · Score: 2, Informative

    This isn't true at all.

    What happens when you have more bugs than you have time to fix? How do you choose which to work on first? How do you remember which ones lead to data loss, and which ones have a workaround? How do you remember how to reproduce each bug? How do you manage patches? How do you remember which patches are compatible with other patches? How do you track the number of reported occurrences of a bug so you can prioritize your fixes more intelligently?

    These things may be pointless in a small project where you can remember all that stuff, but just because it's a one-person project does not mean that it's not too big to get lost in.

    --
    <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
  10. SVN by c0d3r · · Score: 1, Informative

    TortoiseSVN is easy enough to setup to run without a server locally and works great.

  11. Turnkey Redmine by PatDev · · Score: 4, Informative

    http://www.turnkeylinux.org/redmine Seriously. I had an issue tracker running in 5 minutes. By 15 minutes I had the settings the way I wanted it. They ship you a virtual machine image. You load it into VirtualBox and click start. The VM loads to a little screen that tells you what IP address the redmine is running at. It also has git i installed, and it was super quick to migrate my git repo into it. Since I use redmine with git, it's really handy because they are already integrated - when I put "refs #32" in my git commit message, it appears on ticket #32.

  12. org-mode in emacs by hardaker · · Score: 3, Informative

    Emac's org-mode system is fantastic for things like this. It has TODO tracking with scheduling, etc, and you can put one file in each project or one global file for just you, or ... Your choice!

    --
    The next site to slashdot will be ready soon, but subscribers can beat the rush and start slashdotting it early!