From owner-freebsd-java Mon Aug 21 8:37: 0 2000 Delivered-To: freebsd-java@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 1AA2137B424 for ; Mon, 21 Aug 2000 08:36:58 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA18301; Mon, 21 Aug 2000 09:36:56 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id JAA12276; Mon, 21 Aug 2000 09:35:48 -0600 (MDT) (envelope-from nate) Date: Mon, 21 Aug 2000 09:35:48 -0600 (MDT) Message-Id: <200008211535.JAA12276@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: past@netmode.ntua.gr Cc: java@FreeBSD.ORG Subject: RE: JCK License implications (was: State of Server-Side Java) In-Reply-To: <20000821165843.A20089@netmode.ece.ntua.gr> References: <20000821165843.A20089@netmode.ece.ntua.gr> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If I understand things correctly, people with no access to the JCK can still > send patches against patchset 10, and they will be incorporated by the > porting team in the main tree. You got it. > So for everyone else, but the porting team members (both of them :-)), > the native port still IS patchset 10. This way things like native > threads, etc., can still be community-developed and tested. On the money. > The only thing missing will be the patches that the porting team members > make, that provide JCK compliance. That's not too bad IMHO. Except, these *will* be made available 'after the fact', in 'patchset 11' or somesuch, similar to what's being done now for patchset 1-10. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message