Timeline for How do you track bugs in your personal projects?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2012 at 14:13 | history | made wiki | Post Made Community Wiki by Niall Douglas | ||
| Mar 3, 2011 at 21:48 | comment | added | Kevin Laity | @bedwyr Good point, I guess it's a matter of preference. I actually would fix that defect immediately, since we're talking about a small one-man project. If I were in a big corporate setting, different story. | |
| Mar 1, 2011 at 22:57 | comment | added | bedwyr | @Kevin, defects can be found in prior releases while you're working on the latest iteration of a project. Would you immediately halt development on a high-priority feature to fix a low-priority, corner-case defect in a previous version? If not, how do you track them? In my case, a mental list is insufficient. | |
| Mar 1, 2011 at 15:06 | comment | added | Kevin Laity | @bedwyr if you stick to the rule of fixing all known defects before implementing new features, this is a non issue. | |
| Oct 25, 2010 at 18:21 | comment | added | bedwyr | That's partly the problem: a mental list tends to be insufficient. Many of my defects are logged mentally, and then lost over time as new features and enhancements are put in place. | |
| Oct 25, 2010 at 16:11 | history | answered | dsimcha | CC BY-SA 2.5 |