From owner-freebsd-ports@FreeBSD.ORG  Sat May 19 20:51:04 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 48B8116A59A
	for <freebsd-ports@freebsd.org>; Sat, 19 May 2007 20:51:04 +0000 (UTC)
	(envelope-from youshi10@u.washington.edu)
Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu
	[140.142.32.178])
	by mx1.freebsd.org (Postfix) with ESMTP id 2647B13C4B0
	for <freebsd-ports@freebsd.org>; Sat, 19 May 2007 20:51:04 +0000 (UTC)
	(envelope-from youshi10@u.washington.edu)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may
	be forged))
	by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP
	id l4JKp3qM025690
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <freebsd-ports@freebsd.org>; Sat, 19 May 2007 13:51:03 -0700
X-Auth-Received: from [192.168.10.45] (c-67-166-149-71.hsd1.ca.comcast.net
	[67.166.149.71]) (authenticated authid=youshi10)
	by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id
	l4JKp3kc008363
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <freebsd-ports@freebsd.org>; Sat, 19 May 2007 13:51:03 -0700
Message-ID: <464F6336.7040808@u.washington.edu>
Date: Sat, 19 May 2007 13:51:02 -0700
From: Garrett Cooper <youshi10@u.washington.edu>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: freebsd-ports <freebsd-ports@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604,
	Antispam-Data: 2007.5.19.133041
X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0'
Subject: Ports tree : Xorg-7.2 release freeze, ETA?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 May 2007 20:51:04 -0000

Hello,

	The gist of the email is asking the age old question, "are we there yet?"

	As many have commented there are a number of issues with a variety of 
ports which need to be addressed. Some I've noticed are net/samba3 and 
sysutils/eject, which contain security issues affecting production 
workstations and servers.

	Question for the future:

	Wouldn't it be sufficient to force major component testers (in this 
case Xorg 7.2) to use periodic snapshots of the ports tree (possibly CVS 
branching), while allowing continued development in the ports tree? Part 
of my concern is based in the fact that this might be causing issues 
with customer integrity, thus degrading confidence in FreeBSD as a 
production product.

Thanks,
-Garrett