From owner-freebsd-ports@FreeBSD.ORG Mon May 7 18:38:53 2007 Return-Path: X-Original-To: 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 74E9E16A400 for ; Mon, 7 May 2007 18:38:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with SMTP id 2E02513C469 for ; Mon, 7 May 2007 18:38:48 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 7205 invoked by uid 399); 7 May 2007 18:38:45 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 May 2007 18:38:45 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <463F7236.4080108@FreeBSD.org> Date: Mon, 07 May 2007 11:38:46 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Kris Kennaway References: <20070502193159.GB42482@xor.obsecurity.org> In-Reply-To: <20070502193159.GB42482@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: HEADS UP: xorg upgrade plans 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: Mon, 07 May 2007 18:38:53 -0000 Kris Kennaway wrote: > Hi all, > > After many months of hard work (mostly by flz@, as well as others) we > are approaching readiness of the xorg 7.2 upgrade. Because this is a > huge and disruptive change, we're going to approach it very carefully. Good news that this is moving forward! Congrats to all involved. > The current plan is the following: > > 2) Final prep work in git repository. We need a day or two to confirm > the upgrade method for users. Unfortunately testing has exposed a > critical deficiency in portupgrade so 'portupgrade -a' will not be > enough to give a working upgrade, and some pre-upgrade steps will be > required. Has portmaster been evaluated as an upgrade tool? I'm in a better position atm to be able to address any deficiencies if that will help speed this along. > Also a post-upgrade step is required to deal with merging > remaining files from /usr/X11R6 into /usr/local. > > 3) Once the proposed upgrade method is in place, we will publish a > tarball of the prepared ports tree and request that *all* our ports > developers test the upgrade on their own machines before it is > committed to CVS. There are many things that can go wrong and we need > to make sure that the upgrade goes as smoothly as possible for our > less technical users. In particular all ports committers are expected > to participate in this process of eating our own dogfood :) Any updates on a timeline for this? > 4) Once a suitable number of success reports (e.g. 50) are received > and all reported issues are resolved, we'll proceed with importing > into CVS. > > 5) CVS will stay frozen for a period to be evaluated (probably another > couple of weeks) to deal with the inevitable remaining fallout as > users encounter yet more problems with the upgrade. Do you intend to keep the entire ports tree frozen for weeks? Perhaps I misunderstand? Doug -- This .signature sanitized for your protection