From owner-freebsd-ports@FreeBSD.ORG Sun Nov 14 16:41:30 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 391D61065673; Sun, 14 Nov 2010 16:41:30 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 186708FC14; Sun, 14 Nov 2010 16:41:29 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 55FB856028; Sun, 14 Nov 2010 16:41:29 +0000 (UTC) Date: Sun, 14 Nov 2010 16:41:29 +0000 From: Mark Linimon To: Andriy Gapon Message-ID: <20101114164129.GA18379@lonesome.com> References: <4CD7C15D.2010203@icyb.net.ua> <20101108150306.GB17517@wep4035.physik.uni-wuerzburg.de> <4CD8132D.9090902@icyb.net.ua> <20101113192506.GC29660@lonesome.com> <4CDEE881.201@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4CDEE881.201@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Alexey Shuvaev , freebsd-x11@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: xorg-server 1.7.7 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 16:41:30 -0000 On Sat, Nov 13, 2010 at 09:35:29PM +0200, Andriy Gapon wrote: > Not sure if we've had any problems like that when upgrading between minor > versions of a single module, even such as xorg server. I don't remember, either. > That is, I am sure there will be a lot of testers if the port update is > actually committed :-) but I am not sure how to test it in advance (given all > the possible hardware and software configurations). rnoland was doing testing with some of the "well-known" configurations, to make sure those didn't regress. I'd be happy to see various folks step forward to volunteer to beta-test new updates on various configurations. Obviously, 100% coverage is impossible, but if we had a handful of folks, I think we could do a lot. mcl