From owner-freebsd-current Fri Jan 31 17:23:48 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA5FD37B401 for ; Fri, 31 Jan 2003 17:23:46 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5625843F75 for ; Fri, 31 Jan 2003 17:23:46 -0800 (PST) (envelope-from linimon@lonesome.com) Received: from lonesome.lonesome.com (cs2876-77.austin.rr.com [24.28.76.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id 1D5B614343 for ; Fri, 31 Jan 2003 19:23:40 -0600 (CST) Content-Type: text/plain; charset="us-ascii" From: Mark Linimon Organization: Lonesome Dove Computing Services To: freebsd-current@FreeBSD.ORG Subject: State of the Union Report (backout request department) Date: Fri, 31 Jan 2003 19:26:12 -0600 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301311926.12431.linimon@lonesome.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (This is just a view from the sidelines; I generally do ports hacking and not kernel hacking, and thus my views might not carry much weight, but here goes anyways). One of the more interesting features of the FreeBSD development model seems to me to be the ability for people to request controversial CVS commits to be backed out pending further technical discussion. IMHO this seems like a wise (albeit nonintuitive) plan to avoid meta-discussions about what should and should not have been committed by whom and reviewed by whom (and so on and so forth). But recently (especially since the 5.0 release) the backout request mechanism seems to have fallen on hard times. Without too much difficulty, I was able to find 5 separate backout requests in this year's archive of cvs-all alone which were not quickly honored. (I'm not counting an ignored request for which the underlying change was apparently security-related). I'm not sure, but there may have been others, possibly on freebsd-current. The point I'm trying to make by posting this is not to take sides with anyone, assign blame or credit, or anything like that. I personally came up in the old Usenet days, and thus have already gone down that same road so many times that I would hope I've earned a lifetime=20 "Get-Out-Of-Flames-Free" card for that reason alone (never mind various mailing lists and other places controversy loves to incubate ....= ) But if we've got that model, it seems to me we ought to honor it, even if (especially if?) we think the request is frivolous or ill-intentioned. After all, if the backout request itself wasn't controversial, it would probably imply the original change wasn't controversial, and thus who would care to ask to back it out in the first place? I'm just asking folks to think about this so that the whole FreeBSD project can move forward and ideas can rise and fall on their technical merits, because frankly that's where the strength of FreeBSD lies -- in its technical merits. Mark Linimon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message