From dev-return-34980-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Tue Sep 09 03:03:22 2008 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 5302 invoked from network); 9 Sep 2008 03:03:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Sep 2008 03:03:22 -0000 Received: (qmail 82316 invoked by uid 500); 9 Sep 2008 03:03:18 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 82286 invoked by uid 500); 9 Sep 2008 03:03:18 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 82272 invoked by uid 99); 9 Sep 2008 03:03:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 20:03:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wuyuehao@gmail.com designates 209.85.142.188 as permitted sender) Received: from [209.85.142.188] (HELO ti-out-0910.google.com) (209.85.142.188) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 03:02:19 +0000 Received: by ti-out-0910.google.com with SMTP id y6so1123652tia.18 for ; Mon, 08 Sep 2008 20:02:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=qh8GBCpkS1ahyMQSCndGLIkFZ3y1jYI41fvXdxLgjF4=; b=n0nznLv4EavbfuZ6VARzOwbRLB7teK3RNStTDThWyn8pxq7Of5pDetbsSTQkElj0SO b/iz7ZO2Ek2ZbEhruDjIrTzRp9Ifq9ycVZmZ7IvwR2UyRHlpn9cqt1Zvp0uPCeolEJUD /yLvIwNLtJIow2a6+G5G5gqmQzIiQjGJcK8ag= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=OTbT+h+wkhmb1geHTj2ezY0PC3IwoU60gicc4rnGVbGuFvM6526/F0EiqFilE8soH5 TTLyAlYIHiExHRsr4vJlYF+MAU1+y9aFHMVSixOFnbpqlQ2peRX99k9GPwTNAqBbMBtn Y67veL7W1/iz/m9Ny4MxhUoa9okQWtc4zxnQ4= Received: by 10.110.109.12 with SMTP id h12mr21130572tic.34.1220929352368; Mon, 08 Sep 2008 20:02:32 -0700 (PDT) Received: by 10.110.20.14 with HTTP; Mon, 8 Sep 2008 20:02:32 -0700 (PDT) Message-ID: <211709bc0809082002w4f7271ect7a4193c00abf6a8e@mail.gmail.com> Date: Tue, 9 Sep 2008 11:02:32 +0800 From: "Tony Wu" To: dev@harmony.apache.org Subject: Re: [classlib][concurrent] Proposal - move all code into enhanced section In-Reply-To: <3b3f27c60809081826w1f2609f2i440d9a0a0c97e475@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3b3f27c60809081826w1f2609f2i440d9a0a0c97e475@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I agree. svn's external link strikes time to time. We can copy the code from standard to enhanced, so that the concurrent in enhanced acts as a branch of that in standard. Whenever we want to update these code(I believe it's not frequent), just simply do 1. sync standard with [3] above 2. merge to enhanced 3. commit If we dont need to modify these code from Doug Lea (we have never done that before?), this model could be completed by an automatic script. On Tue, Sep 9, 2008 at 9:26 AM, Nathan Beyer wrote: > I've mentioned this on the list before, but I'd like wrap it up. I'd > like to propose moving all of the code from the concurrency module > that's in the standard folder [1] into the enhanced folder [2]. There > are a couple of reasons for doing this. > > * The separation complicates the source maintenance and builds. One > original intention was to keep the code somewhat protected, but I > think the same diligence and discretion can be applied to the code in > the enhanced folder. > * The original code is public domain. Based on a few conversations > I've had and my reading, we should really just take ownership of the > source and mark it all as AL (put the AL header in the files). > > Working model going forward > * To help managing the code that we pull from the concurrency repo > [3], we can continue to commit the unmodified code into appropriately > named folders in standard. The names could reflect tag names from the > original SCM. We can do this periodically. > * Periodically merge code from the latest code pulls into the enhanced branch. > * Continue to modify the concurrency code only on rare occasions and > always get mailing list approval for the changes. > > Comments, thoughts, objections? > > -Nathan > > [1] https://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/ > [2] https://svn.apache.org/repos/asf/harmony/enhanced/classlib/trunk/modules/concurrent/ > [3] http://gee.cs.oswego.edu/dl/concurrency-interest/ > -- Tony Wu China Software Development Lab, IBM