On 3 ago, 17:23, björn <[email protected]> wrote: > > On 3 August 2010 08:17, H.P. Logsdon wrote: > > I prefer if issue reports/feature requests/patch submissions are made > to this list so that other people may respond to them and in the > process taking some of the load off me. That being said, if somebody > has something favorable to say of issue trackers (and the GitHub one > in particular) I may be convinced to start using them in earnest. > Maybe I am just not using the "correctly"?
In my view, the main benefit of an issue tracker over a mailing list is that it provides a sortable, searchable "memory" that ensures that you never overlook or forget about an issue. The cost of this, as you've described, is the maintenance overhead (closing duplicates, distinguishing real bugs from support requests etc). It's up to each project to decide if the advantage of this "memory" is worth the costs. There are some successful open source projects out there which don't have issue trackers and use their mailing lists as their bug reporting and management mechanism. A good example is the Git project. Then there is a middle ground: using the mailing list as the bug reporting forum, and you maintaining your own internal issue tracker (using anything from a text file to a "To Do List" application) to ensure that you don't ever forget anything. I've read quite a few developer blog posts which reveal that there are lots of developers out there that work in this way. I personally find that the benefits of a public issue tracker outweigh the costs. Specifically with regards to the GitHub one, however, I find it to be a bit klunky. If the choice is between using the mailing list and using GitHub issues, I'd use the mailing list... Cheers, Wincent -- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
