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

6 of 221 comments (clear)

  1. Try Trello by Anonymous Coward · · Score: 5, Interesting

    Try Trello, it is simple enough to use, free and cloud based.

    https://trello.com/

  2. Re:Dead project mining. by jellomizer · · Score: 4, Interesting

    Unless the project died from improperly managing bugs...

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  3. Use SourceForce.net by ckthorp · · Score: 1, Interesting

    Just create a dummy SourceForce project. You don't actually have to attached any source files to use the bug tracker or other features.

  4. Call me old fashioned, but... by JustAnotherIdiot · · Score: 3, Interesting

    ...I prefer to list out stuff like that in a journal using pen/paper.
    I get a great personal satisfaction drawing a line through fixed bugs over just deleting a line of text or checking a box.

    --
    What do I know, I'm just an idiot, right?
  5. Re:bugs.txt by Rob+Kaper · · Score: 4, Interesting

    I wrote find-issues.sh, a script that extracts comments of a certain type within the code and then groups them by file. Downside: your code files change when you register a bug. Upside: when done right, your bug description is next to the code that needs fixing.

    Obviously won't work for distributed development, but for single-coder projects, it's really been useful to me.
    Note some assumptions and grep magic to exclude third-party files and other non-code files.

    #!/bin/sh

    LASTFILE=""
    egrep -ri "(WARNING|HACK|FIXME|TODO|BUG)" . | egrep -vi "(\.git|debug|/third-party|/locale|/prettify|doc/|/jquery-|lib/s3.php|/jwysiwyg/|^./(.*)\.(txt|conf|xml):(.*))" | while read LINE ; do
            FILE=`echo "${LINE}" | cut -d":" -f1`
            DATA=`echo "${LINE}" | cut -d":" -f2- | cut -d"/" -f3-`
            LEVEL=`echo "${DATA}" | cut -d":" -f1`
            COMMENT=`echo "${DATA}" | cut -d":" -f2-`

            if [ "x${LASTFILE}" != "x${FILE}" ]; then
                    if [ "x${LASTFILE}" != "x1" ]; then
                            echo
                    fi
                    printf "%s:\n" "${FILE}"
                    LASTFILE=${FILE}
            fi
            printf "%5s:%s\n" "${LEVEL}" "${COMMENT}"
    done

  6. Re:bugs.txt by gauauu · · Score: 3, Interesting

    Cool idea. What do you do when there's a bug but you don't know where in the code that it's caused?