From owner-freebsd-arch@FreeBSD.ORG Thu Sep 2 08:18:24 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E41616A4D7 for ; Thu, 2 Sep 2004 08:18:24 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8D6443D31 for ; Thu, 2 Sep 2004 08:18:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i828Fawl090687; Thu, 2 Sep 2004 02:15:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 02 Sep 2004 02:15:49 -0600 (MDT) Message-Id: <20040902.021549.54181743.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <4136D0A4.9000407@elischer.org> References: <20040902051415.GA23926@odin.ac.hmc.edu> <4136D0A4.9000407@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: arch@freebsd.org cc: drosih@rpi.edu Subject: Re: if_data size issues X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2004 08:18:24 -0000 In message: <4136D0A4.9000407@elischer.org> Julian Elischer writes: : yes I believe 5.2->6.0-current@X : where X is a point in time a bit down the road, is not an important : conversion, as very few people will be doing it... : those who are running 5.2 will probably jump to either 5.3 or 6.0 : within a relatively short time. The current plans for the rest of the build system is to support 5.2 (or maybe 5.1) -> 6-CURRENT upgrades. This is a larger window than we had for the 5-current branch (which was 4 branchpoint -> current), but seems like a reasonable compromise. In the past, when core and non-core discussions of this have come up, stable branchpoint -> current was the compromise window of upgrade path that would be allowed in the tree to balance the needs of the users to upgrade, with the needs of the developers to do spring cleaning. There is much history of discussions here, and much behind the scenes negotiation to reach this compromise. : those who go to 6 from 4 will probably go to 4.11 or more or 5.3+ first. 4.x -> 6-current will need to go through 5.x (x >= 2) after 5.3 is released. Warner