From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 09:09:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2004D16A4B3 for ; Tue, 16 Sep 2003 09:09:36 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 955E243F93 for ; Tue, 16 Sep 2003 09:09:33 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 77375 invoked by uid 1002); 16 Sep 2003 16:09:33 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 16 Sep 2003 16:09:33 -0000 Message-ID: <3F6735B7.9050109@freebsd.org> Date: Tue, 16 Sep 2003 10:09:27 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Moran References: <3F66A446.7090408@freebsd.org> <20030916131622.N54869@news1.macomnet.ru> <20030916200513.R4917@gamplex.bde.org> <3F672308.1080909@freebsd.org> <3F673285.8080903@potentialtech.com> In-Reply-To: <3F673285.8080903@potentialtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Mike Silbersack cc: tegge@freebsd.org cc: current@freebsd.org Subject: Re: Release Engineering Status Report X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 16:09:36 -0000 Bill Moran wrote: > Scott Long wrote: > >> Bruce Evans wrote: >> >>> On Tue, 16 Sep 2003, Maxim Konovalov wrote: >>> >>>> PAE MFC brought an incredible instability to stable branch. It >>>> affects 100% of our user community especially when we issued several >>>> SAs since PAE commit. They often can't switch to RELENG_4_x security >>>> branches because even RELENG_4_8 misses several critical non-security >>>> fixes. >>> >>> >>> I merged PAE into my version of -current a bit at a time and didn't >>> notice any problems (with PAE not actually configured) despite having >>> some large logical inconsistencies from not having all of it. Most >>> of the global changes had no effect since they just changed the names >>> of some typedefs without changing the underlying types in the !PAE >>> case. So I suspect that any instabilities in RELENG_4 in the !PAE >>> case are indirectly related to PAE and/or localized and thus easy to >>> find and fix. >>> >>> Bruce >> >> >> Agreed. PAE was merged into -stable in three steps. Backing out the >> third step and leaving the first two steps removes the instability. >> Unfortunately, it was the third step that also was the most complex. >> In any case, we have 2 weeks to find the resolution before the decision >> must be made on keeping or tossing PAE. Since PAE is a *highly* >> sought after feature, it would be doing a disservice to our user base >> to remove it without putting in some effort to fix it. > > > If someone who was involved in this would publish the date on which that > last commit was made, people who are experiencing problems, but wish to > stay as close to -STABLE as possible can use cvsup to revert their trees > to a date immediately prior to the commit. > > This will solve both problems for now: i.e. the problem of users wanting > the bugfixes/new features of -STABLE will have a target they can cvsup to > that is reliable, while the developers can continue to pursue their goal > of having PAE in 4.9. > Patches have been floated on the mailing list that revert PAE in its various stages. Maybe those need to be brought back up. Silby? Tor? Scott