Bug tracker for any decent sized project seem like a bit of a no-brainer to me - it makes it really easy to organise hundreds or thousands issues, without issues colliding or getting mixed up.So when I see some really big projects, like Git, using a mailing list as the main method of coordinating maintenance and development, I get a bit blown away. Examples:Git - Community page:...Bug reports should be sent to this mailing list.Debian bug tracking system, per Wikipedia:...Its unique feature is that it doesn't have any form of web-interface to edit bug reports - all modification is done through email.Many modern bug trackers have very good integration with email (you can receive comments or notifications about bugs you're watching, or that get assigned to you), as well as to version control systems (commits can be marked as resolving an issue, etc.). Much of this would have to be done manually with a mailing list, and you get tons of emails about bugs you're not interested in.So what are the main advantages of a mailing list over a web-based bug tracker? Why do some big projects only use a mailing list?
Why do some big projects, like Git and Debian, only use a mailing list and not an issue tracker?
project management;communication;issue tracking;email