From owner-freebsd-ports@FreeBSD.ORG Wed May 2 22:40:51 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 43C9716A401 for ; Wed, 2 May 2007 22:40:51 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 323BA13C44C for ; Wed, 2 May 2007 22:40:51 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5E68A1A4D89; Wed, 2 May 2007 15:41:25 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 65F8951406; Wed, 2 May 2007 18:40:50 -0400 (EDT) Date: Wed, 2 May 2007 18:40:50 -0400 From: Kris Kennaway To: Gerald Pfeifer Message-ID: <20070502224050.GA45434@xor.obsecurity.org> References: <20070502193159.GB42482@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: ports@FreeBSD.org, Kris Kennaway 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: Wed, 02 May 2007 22:40:51 -0000 On Wed, May 02, 2007 at 11:36:03PM +0200, Gerald Pfeifer wrote: > On Wed, 2 May 2007, Kris Kennaway wrote: > > In particular all ports committers are expected to participate in this > > process of eating our own dogfood :) > > Our marketing folks educated me to use the phrase "drinking our own > champagne" instead. :) ;-) > > 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. > > Does this freeze apply to the whole ports tree, or only (relatively > directly) affected parts of the tree? For example, does this also > apply to lang/gccXY? It will apply to everything. It will be basically the same procedure we usually use for a release cycle, since this event is easily comparable in scope (probably bigger in fact). The good news is that if we all jump in to help, the freeze will be over sooner. Kris