From owner-freebsd-threads@FreeBSD.ORG Wed Jan 7 18:12:07 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFF0A16A4CE; Wed, 7 Jan 2004 18:12:07 -0800 (PST) Received: from mhub-m5.tc.umn.edu (mhub-m5.tc.umn.edu [160.94.23.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8638843D2F; Wed, 7 Jan 2004 18:12:06 -0800 (PST) (envelope-from ryans@gamersimpact.com) Received: from [24.107.70.120] by mhub-m5.tc.umn.edu with ESMTP; Wed, 7 Jan 2004 20:12:05 -0600 From: Ryan Sommers To: Robert Watson In-Reply-To: References: Content-Type: text/plain Message-Id: <1073527914.650.41.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 07 Jan 2004 20:11:55 -0600 Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: Release criteria for libkse -> libpthread switch? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 02:12:07 -0000 On Wed, 2004-01-07 at 19:39, Robert Watson wrote: > My leaning is we should throw the switch to libkse sooner rather than > later to improve exposure, even though it's not quite feature complete. > It was basically an accident of timing and intent that we didn't get to > the rename before 5.2. For one thing, it will get applications to start > linking against libpthread sooner. However, if we're going to throw the > switch, it would be good to know the features aren't far behind :-). > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research My only concern with this is that it might cause some sort of delay in getting to 5-STABLE. I think, as I'm sure most would agree, that achieving a 5-STABLE is the next major milestone for the project. One that, from the lists, some think is somewhat overdue. -- Ryan Sommers ryans@gamersimpact.com