11–17 of 17 posts
I don't think we need another bug tracker - bugzilla and trac do a great job already. What I'd love to have is a command line interface to existing bug trackers.
It could use some love as contributions have dropped off and I haven't had time to maintain it myself for quite a while.
However, it is quite useable.
I don't think we need another bug tracker - bugzilla and trac do a great job already. What I'd love to have is a command line interface to existing bug trackers.
Not that there's anything wrong with the other two, but Redmine is miles ahead, in my opinion.
I don't think we need another bug tracker - bugzilla and trac do a great job already. What I'd love to have is a command line interface to existing bug trackers.
It syncs with various online bug trackers and supports full offline manipulation of the bugs. I would use it if I didn't just make a list of stuff to do in a text file.
Earlier quoted context omitted.
Stolen from ditz: - create a simple website form for bug reports, which emails to the project mailing list, where all discussion should happen anyways - let a bot scan the mailing list for bug reports and commit them, wherever suited
Why should all discussion happen on the mailing list?
Earlier quoted context omitted.
When you init it, it creates a .later directory to store the issues. You could revision this along with code, so yes it seems like a nice replacement to the todo.txt.
Playing a bit more, what would be really nice would be to be able to do later -r list to recurse through subdirectories listing issues in those too. At present it only looks upwards.