On Thu, 04 Jan 2018 06:16:45 +0000, codephantom wrote: > This is not my area of experise, but, if I were a manager evaluating the > merits of D for use in a corporate software project, and then I went off > to bugzilla and looked at the items for D.. I'd pause and think.....wtf > is going on here. > > I don't know how other open source projects manage this, or how other > mainstream languages manage this, but I would assume there are 'best > practices' out there...somewhere. > > I doubt very much whether just allowing stuff to pile up in some > bugzilla repository, is a best practice.
At the time of writing: Ansible has 3391 open bugs[1] (and ~master is often used in production). Python has more than 6000, 2000+ with patches[2]. GCC (C and C++ components only) has 3119[3]. Bugs are part of software. That's just life. It doesn't mean the software is unreliable/unusable, just that it can be better. [1]: https://github.com/ansible/ansible/issues [2]: https://bugs.python.org/issue?@template=stats [3]: https://gcc.gnu.org/bugzilla/report.cgi? x_axis_field=&y_axis_field=bug_status&z_axis_field=&no_redirect=1&query_format=report- table&short_desc_type=allwordssubstr&short_desc=&product=gcc&component=c&component=c %2B% 2B&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&cf_gcchost_type=allwordssubstr&cf_gcchost=&cf_gcctarget_type=allwordssubstr&cf_gcctarget=&cf_gccbuild_type=allwordssubstr&cf_gccbuild=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap
