From owner-freebsd-python@freebsd.org Tue Sep 24 03:00:40 2019 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7F499F4D3C for ; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46cmCX2qN3z3QDy for ; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 60D7FF4D3A; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 609FAF4D39 for ; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46cmCX1ww8z3QDx for ; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 25F5B20C4B for ; Tue, 24 Sep 2019 03:00:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8O30eQw076319 for ; Tue, 24 Sep 2019 03:00:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8O30ekX076318 for python@FreeBSD.org; Tue, 24 Sep 2019 03:00:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240774] security/py-fido2: Update to 0.7.1 Date: Tue, 24 Sep 2019 03:00:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: grembo@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2019 03:00:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240774 --- Comment #9 from Kubilay Kocak --- (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.=