From owner-freebsd-arch  Wed May 24 20:42:16 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1])
	by hub.freebsd.org (Postfix) with ESMTP id B687537BA56
	for <arch@freebsd.org>; Wed, 24 May 2000 20:42:12 -0700 (PDT)
	(envelope-from cp@berserker.bsdi.com)
Received: from berserker.bsdi.com (cp@[127.0.0.1])
	by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id VAA17364;
	Wed, 24 May 2000 21:42:06 -0600 (MDT)
Message-Id: <200005250342.VAA17364@berserker.bsdi.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Matthew Dillon <dillon@apollo.backplane.com>, arch@freebsd.org
Subject: Re: Short summary 
From: Chuck Paterson <cp@bsdi.com>
Date: Wed, 24 May 2000 21:42:05 -0600
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	While it will be true that the tree will be broken sometimes
I personally believe that in general it has to be kept running.
You might not want to use it for any real work. The reason being
that these changes are way to big to debug all at once.

Chuck

}
}I think it's also fair to say that we'd be willing to accept a certain
}period of outright breakage in FreeBSD-current if it gets us to the
}right place, e.g. a painless transition is not necessarily the goal so
}much as getting things done right.  We've gone through similar periods
}with -current in the past and nobody had too much difficultly with the
}concept provided that we ANNOUNCED it well in advance and told the
}cvsuppers to basically turn their cron jobs off or elect not to try
}and build the world until the tree was declared safe again.
}


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message