Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

a plain text TODO file within the repository of each project, together with a plain text TODO file in my dropbox that gets synced everywhere. Works very well.


I really like this kind of solution for smaller projects, where a proper bug tracker is excessive overhead. Keep everything in the repo and it's much simpler to maintain.

Do you have a formal-ish system for this? Notice issue -> TODO -> write unit test -> fix issue -> cut + paste to ChangeLog?


We work in a 3 person team max, and run a project management tool/CRM next to it (apollo) so there is no need to do communication via special protocols. We tried a bunch of them and it just doesn't work for small teams. We live in GIT anyway, so a todo.txt is a really good solution.

It's mostly: email to say bugs need fixing -> bugs get fixed -> fix gets committed and the bug removed from the todo -> email back that it's fixed.

It mostly concerns visual (html/css/templating) bugs or small js bugs that don't have unit tests/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: