Anselm R Garbe <garb...@gmail.com> writes: > IMHO this view is short sighted. The point of an _issue_ tracker (not > every issue is a bug) is not the possibility to flood the developer > with random bug reports, but to provide a simple infrastructure to > organize and priotize a TODO list for the development of a certain > project -- AND also to document the development, why some decision was > made at some point in time. The idea for a suckless issue tracker is > to make it mailing-list based, so that one can work with it with plain > mails. It thus also allows discussions and patches.
I agree with this view of the issue tracker.
