Ask Slashdot: How Do You Track Bugs For Personal Software Projects? 221
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?"
Post a Press Release. (Score:5, Funny)
After every bug in my project you post a press release, discrediting the person who found the bug as some subversive agent, and explaining its uses of the bug in a positive light.
After the press release is done, I like to go into a dark room with a rocking chair, plug my ears and go LA LA LA really loudly until someone else says there is an other bug.
Dead project mining. (Score:4, Funny)
Find a dead project online, and hijack their bug tracker. Just as long as it's one where you can register without authorization and close your own bugs it should work brilliantly.
Bug tracking is too much work (Score:1, Funny)
I find it easier not to put bugs in my code.
Wait a second... (Score:5, Funny)
I'm confused. You actually keep track of problems with your personal projects in the hopes of completing them one day?
I must be doing it wrong because I start a project and as soon as i get to the first major design issue, or meal time, i quit.
so i don't really ever have any bugs, per se. but i do have an svn with a sh*tload of half ass projects that i can let you have real cheap.
Re:Dead project mining. (Score:5, Funny)
Re:todo.txt (Score:5, Funny)
I file mine in my todo.txt, which also includes missing features. Since I don't do a release if there are *any* known outstanding bugs, "bugs" and "incomplete features" are essentially the same for me.
So you never release?