Slashdot Mirror

← Back to Stories (view on slashdot.org)

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

Posted by timothy on from the when-bugzilla-is-a-monster dept.

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?"

2 of 221 comments (clear)

  1. bugs.txt by Anonymous Coward · · Score: 5, Insightful

    check it in with your code, add and remove bugs as needed. 5 seconds of setup. Search and has a history.

  2. Re:highlighted comments in source by LodCrappo · · Score: 5, Insightful

    > What happens when you have more bugs than you have time to fix?

    You put a quick note in with a TODO tag

    > How do you choose which to work on first?

    You switch to a view that shows all your TODO tags and take your pick

    > How do you remember which ones lead to data loss, and which ones have a workaround?

    You type those details into the TODO tag

    > How do you remember how to reproduce each bug?

    See above

    > How do you manage patches?

    diff on commit = patch. no big deal.

    > How do you remember which patches are compatible with other patches?

    whatever man, you are really reaching here. make all patches compatible with all others, or pay the price. this is a personal project.

    > How do you track the number of reported occurrences of a bug so you can prioritize your fixes more intelligently?

    again, simply add this type of detail to your TODO tag

    --
    -Lod