Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 28601 invoked from network); 27 Apr 2007 06:43:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Apr 2007 06:43:25 -0000 Received: (qmail 56457 invoked by uid 500); 27 Apr 2007 06:43:31 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 55904 invoked by uid 500); 27 Apr 2007 06:43:29 -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 55894 invoked by uid 99); 27 Apr 2007 06:43:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2007 23:43:29 -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 alexey.a.petrenko@gmail.com designates 64.233.162.239 as permitted sender) Received: from [64.233.162.239] (HELO nz-out-0506.google.com) (64.233.162.239) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2007 23:43:22 -0700 Received: by nz-out-0506.google.com with SMTP id j2so1085701nzf for ; Thu, 26 Apr 2007 23:43:01 -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=YZ8g6KonJkwiKsaP+FXDnzX/x+ntHimabG1O07Kj3+okzOsnS3itB/dKo+Gln2RfDQ2hNXt6hOpBt62DuxD445tI+p1DXyo2kXWkrJmfHM0bN51vn5HuNjm0qA3VQl+MQgWyjtG/FhWVtx1+ktURXwsVCGvwc4lf7ji8kTicthc= 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=FLKXsEYyLNlnvCzCZ1b6H4MaxkiaMOIJZTmRyi3U/eACtxJT3urHyMJe8uIB6zS4QsOBUeP1uch1wgQaf8qgD29nkfy08hHcWct8t7tHhj9xbYc1aBlxAEob5ZGd9fRXbzN6tKVXx6VtrFnXfMnfAJhea5XgaeT0wAMVcMnM+1M= Received: by 10.114.169.2 with SMTP id r2mr912102wae.1177656181344; Thu, 26 Apr 2007 23:43:01 -0700 (PDT) Received: by 10.114.123.16 with HTTP; Thu, 26 Apr 2007 23:43:01 -0700 (PDT) Message-ID: Date: Fri, 27 Apr 2007 10:43:01 +0400 From: "Alexey Petrenko" To: dev@harmony.apache.org Subject: Re: [snapshot] Freezing the code for Milestone build? In-Reply-To: <4630B6F7.7080705@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46306E6A.60204@gmail.com> <906dd82e0704260240m5eaef815g29b7113a6bf24892@mail.gmail.com> <46307C1C.9020000@gmail.com> <253b20230704260334h765678d9qdb7ecd45df4903af@mail.gmail.com> <9623c9a50704260348k7008e12axd6adaa2e1ee8a6ee@mail.gmail.com> <4630B6F7.7080705@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org DRLVM has been switched back to GCv4. HARMONY-3764 "[drlvm][build] jar with kernel classes' sources is not generated" has been resolved Patch for HARMONY-3730 "[drlvm][jvmti] SINGLE_STEP events are not reported in JIT mode" has been applied but the issue is not closed. Gregory, do you have anything to do with this issue or you just forgot to press resolve button? :) SY, Alexey 2007/4/26, Tim Ellison : > Xiao-Feng Li wrote: > > On 4/26/07, Sergey Kuksenko wrote: > >> Hi All, > >> > >> I wish to notify that GCv5 currently has a stability problem. > >> > >> http://issues.apache.org/jira/browse/HARMONY-3746 > >> I think We should fix the bug before freese or switch back to GCv4.1. > >> > > > > I noticed that, and am trying to reproduce it, so far can't reproduce > > it locally. I am now trying to connect the test machine to check the > > problem. Hopefully it can be fixed quite soon within two days. > > Otherwise, I'd vote to switch it back to GCv4.1. > > > > The other solution would be to choose a revision and make a release > > branch from it. Then we don't need to freeze the code base for new > > developments. This is actually common for industry product release. > > Ok, let's wait and see what you conclude. > > Regards, > Tim >