Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 57419 invoked from network); 23 Apr 2007 10:46:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2007 10:46:48 -0000 Received: (qmail 22517 invoked by uid 500); 23 Apr 2007 10:46:52 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 22488 invoked by uid 500); 23 Apr 2007 10:46:52 -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 22479 invoked by uid 99); 23 Apr 2007 10:46:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2007 03:46:52 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ilya.neverov@gmail.com designates 209.85.132.245 as permitted sender) Received: from [209.85.132.245] (HELO an-out-0708.google.com) (209.85.132.245) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2007 03:46:44 -0700 Received: by an-out-0708.google.com with SMTP id b2so1913134ana for ; Mon, 23 Apr 2007 03:46:24 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oI4HIZKLJfiqA10bi3JEIFPUNUzMhQ3XH7tBgBmRJDbYC47b/FBGXQSmZ8gqYA98Wji2Iy5ietWRwlpqUZSi6K7GVZE34O4dnC7bcVwSQWsk8R+vsk34SU68lEFqvipVdDWgs/HGqKSvRmBNOS+gvk0r/xdS7B3QxZn9rwZBQYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tRxpte4OUmYCAG4vX3cS5R1nfpSM/bc007bYyvbXQkdR/cI80rdULqHmiepUwB7dbeV1hJb9TWmajkFi4dAhfZxY1od9DHb1jVFwNlmsSVwiS3COXu3nY7YU8sRPVTZ8XRVt/nNQoYUQDbqJx3tvjiWnLxDxZnTfrzIIE0U1fXs= Received: by 10.100.124.5 with SMTP id w5mr3532947anc.1177325184006; Mon, 23 Apr 2007 03:46:24 -0700 (PDT) Received: by 10.100.177.13 with HTTP; Mon, 23 Apr 2007 03:46:23 -0700 (PDT) Message-ID: <4ed33be10704230346h2e873162x8127fbffb3815924@mail.gmail.com> Date: Mon, 23 Apr 2007 17:46:23 +0700 From: "Ilya Neverov" To: dev@harmony.apache.org Subject: Re: [build-and-test] Update: plan for improving of the new testing infra before switching to it. In-Reply-To: <6e47b64f0704230325x33d54a90p3e7a52cfe1dc2341@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6e47b64f0704230325x33d54a90p3e7a52cfe1dc2341@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org > To make further progress I think it makes sense to commit the > implementation from [2] to SVN as it is. And continue development and > bug fixing in SVN. [+1] I believe it will make development of that infra more productive. I support approach with the '2.0' sub-directory of 'trunk'; no need for branch is seen here. Regards, -Ilya On 4/23/07, Stepan Mishura wrote: > Hi, > > I'd like to give an update about current status of buildtest infra. > Currently we have the proposal [1] for the infra improvement, its > implementation [2] and several testing suites that use the proposed > approach. I think that the proposed infra is not quite ready to do the > switch - I've reviewed the implementation and tried 4 suites with it; > I've found several issues and I see some places where it can be > improved. And I believe that the issues should be resolved before > switching to the new testing infra. > > To make further progress I think it makes sense to commit the > implementation from [2] to SVN as it is. And continue development and > bug fixing in SVN. This will make improvement process more > transparent, for example, currently there is tenth version of > 'btinfra.zip' file and it is not possible to figure out what have > changed since its first version. > > I'm not sure that a new branch should be created to check in the new > infra. I think it may be acceptable to create sub-directory in trunk, > say 'v2.0'. And continue the infra development and new suites > integration there. After we find that the new infra in a good shape we > can do the switch. > > Opinions? > > [1] http://mail-archives.apache.org/mod_mbox/harmony-dev/200703.mbox/%3ce09a11790703262343m576dee90j5a59d52e14290274@mail.gmail.com%3e > [2] http://issues.apache.org/jira/browse/HARMONY-3501 > > Thanks, > Stepan Mishura > Intel Enterprise Solutions Software Division > -- Thank you. Ilya Neverov