From owner-java@FreeBSD.ORG Mon Dec 15 15:55:37 1997 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA29072 for java-outgoing; Mon, 15 Dec 1997 15:55:37 -0800 (PST) (envelope-from owner-java@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA29058 for ; Mon, 15 Dec 1997 15:55:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id XAA23186; Mon, 15 Dec 1997 23:55:23 GMT Message-ID: <19971215155522.37546@relay.nuxi.com> Date: Mon, 15 Dec 1997 15:55:22 -0800 From: "David E. O'Brien" To: Brian Behlendorf Cc: boia01@gel.usherb.ca, freebsd-java@FreeBSD.ORG Subject: Re: JDK 1.1.5: Ready, set, go! Reply-To: obrien@NUXI.com References: <3.0.3.32.19971212191058.00900dd0@hyperreal.org> <3.0.3.32.19971215152125.009835f0@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <3.0.3.32.19971215152125.009835f0@hyperreal.org>; from Brian Behlendorf on Mon, Dec 15, 1997 at 03:21:25PM -0800 X-Warning: Mutt Bites! X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-java@FreeBSD.ORG Precedence: bulk > Since what you release is a set of patches, what we would do is import the > 1.1.5 JDK source into the CVS hierarchy, and when we get ready to do a On a vendor branch. > release, do a "cvs diff -R" from the root directory specifying the > differences between the current base and the imported code. Shouldn't be a > problem. That way when one of the developers has the CVS tree checked out > they should be able to test the committed changes by recompiling. The > downside is that we couldn't share access to the CVS tree (including cvsup > read-only access) with anyone who doesn't abide by the Sun license > agreements. Also, when a new JDK comes out (e.g. 1.1.6) we can take the Again commit the new JDK (e.g. 1.1.6) on the Vendor branch. Then it becomes easy to see what changed and where new potential porting problem may be. > In particular I'm somewhat concerned about the Sun license agreements cause > this to be a tricky proposition, If you checked "membership" cards at the door, the effort should be safe. So people would have to prove they've got Sun's OK to the source. Along with the time limit of the OK. > I'm also concerned it may 'taint' the folks here and others involved > from ever being able to work on Kaffe or other clean room Java efforts. > Thoughts? Certainly a concern, but no more than everyone working alone. Has anyone seen this addressed by Sun? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) James says: "Grad school sucks."