Date: Tue, 24 Sep 2019 02:39:13 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240774] security/py-fido2: Update to 0.7.1 Message-ID: <bug-240774-21822-SGBuYjHwfL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240774-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-240774-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240774 --- Comment #6 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Michael Gmelin from comment #3) It does for maintainer-feedback flag (issue level), but not for maintainer-approval (attachment flag/level), so that, the flag state (?) and the value (maintainer email) has to be added manually. It could be automated, but there's issues/considerations: https://wiki.freebsd.org/KubilayKocak/Bugzilla/Roadmap#MAINTAINER_approval_of_patches Re "Severity "(Affects *)" field, the distinctions are: 1) bugs vs features ("updates" are more like features, unless they only fix bugs), so maintainer updates are almost always 'affects only me' on that basis. 2) Objective vs subjective severity. It's difficult to say how many 'actual' people are effected, say based on usage/popularity guesses, but one can 'class' the issue severity based on some objective properties, like: a) global/unconditional bug: Affects many/all b) conditional bug: Affects some. Like a bug with a particular port OPTION or specific base binary argument or other specific condition or set of conditions I'll write something about up in the triaging guidelines. Thanks for asking :) -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240774-21822-SGBuYjHwfL>