https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211353
--- Comment #3 from Kubilay Kocak <ko...@freebsd.org> --- (In reply to John Marino from comment #2) Closing an issue is implicitly taking responsibility for it in the same way a commit in the tree is, as a decision is being made by the closer, whether with a change (commit) or not (rejected, feedback timeout). The scope is (can) not limited to the commit as any followup as a result of that commit is also implicitly related to the issue. The other reason for assignment is for accurate statistics and reporting (who did what when), and the fact that the default assignee of all ports issues being freebsd-ports-bugs (empty or unassigned), so that notifications go somewhere lest they never get actioned(read: assigned then resolved). If everyone used the issue tracker and not mailing lists, then issues would go from unassigned to assigned in that case. Having real assignees set as early as possible reduces the noise:signal ratio for every one else at all points during an issues lifetime, which still remains high. Issues being inaccurately or incompletely classified in the past, assignee or any field, is only evidence of inconsistent/adhoc issue tracking practices, not of a defacto standard. If this constitutes a genuine impact or burden on you, please email bugmeister@ where we can aim to understand the issue in more detail and discuss it in a more amenable manner and place. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
