Date: Tue, 24 Sep 2019 03:00:40 +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-0PbzLzAzRV@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240774 --- Comment #9 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Michael Gmelin from comment #8) Yep. Though to be clearer/more precise, its worth noting: - The default Bugzilla field name is 'Severity', one of the two fields, the other 'Priority', which together make up the 'Importance' field. - Depending on the Labels used, 'Severity' is most often used to mean 'Impa= ct' (default values are like: Enhancement, Minor, Major, Blocker), but can also= be like 'Scope', like for our labels (Me, Some, Many) Also: 'Severity' in other industries (say, medical triage) are basically used as a proxy for 'Urgency', usually based on the notion of 'Impact', but can also include things like is vital function affected' 'Is the issue/symptom degrading', or 'has it / can it be stabilised'. Analogies in bug/issue tria= ge are things like: 'is a workaround available', 'is this a major/important feature' One 'todo' item is to improve the schema for Severity/Priority, to make it = make more sense and have obvious semantic meaning for zero-knowledge people (like reporters). This is not an easy problem :) I'll add it the Roadmap document= to we can start to flesh it and options out more. Happy to soundboard stuff wi= th you if you're interested in this kind of stuff --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240774-21822-0PbzLzAzRV>