From owner-freebsd-current@FreeBSD.ORG Mon May 14 09:55:57 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0B2C16A402 for ; Mon, 14 May 2007 09:55:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 61FB313C44C for ; Mon, 14 May 2007 09:55:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l4E9ttnT001875; Mon, 14 May 2007 19:55:55 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l4E9tt3g001874; Mon, 14 May 2007 19:55:55 +1000 (EST) (envelope-from peter) Date: Mon, 14 May 2007 19:55:55 +1000 From: Peter Jeremy To: Mark Linimon Message-ID: <20070514095555.GE1171@turion.vk2pj.dyndns.org> References: <20070513211036.GA18134@soaustin.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i7F3eY7HS/tUJxUd" Content-Disposition: inline In-Reply-To: <20070513211036.GA18134@soaustin.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.15 (2007-04-06) Cc: freebsd-current@freebsd.org Subject: Re: Process for requesting reverting patch? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2007 09:55:57 -0000 --i7F3eY7HS/tUJxUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-13 16:10:36 -0500, Mark Linimon wrote: >We really need to redefine what 'critical' is, since that field is so >often overused as to be meaningless. That may be on of the topics I try >to address at BSDCan when talking about PR workflow. There are two difficulties here: 1) What is "critical" to me may seem totally unimportant to you. 2) I might just make everything "critical" to make someone look at it (I have lots of developers at work who believe in the latter approach). The approach we used at work was to avoid the "critical/high/medium/low" categories and categorise based on impact instead - which removed much of the subjectivity. --=20 Peter Jeremy --i7F3eY7HS/tUJxUd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGSDIr/opHv/APuIcRAljRAKCLaS25ih4LgNgouCjh7SY5AwkZ4QCgsgaD S2doYMIUp4Li6F5qWm27GQs= =HNpK -----END PGP SIGNATURE----- --i7F3eY7HS/tUJxUd--