Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 39560 invoked from network); 25 Jun 2007 07:15:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2007 07:15:10 -0000 Received: (qmail 46835 invoked by uid 500); 25 Jun 2007 07:15:12 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 46592 invoked by uid 500); 25 Jun 2007 07:15:11 -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 46583 invoked by uid 99); 25 Jun 2007 07:15:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 00:15:11 -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 mloenko@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 00:15:06 -0700 Received: by ug-out-1314.google.com with SMTP id s2so1196545uge for ; Mon, 25 Jun 2007 00:14:44 -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=bcNkBrOg3f+SI6egZpmtdYc81kJSFnu3x6ikn6yWhy+AcqNR3jp34Rew09YbJ3SeTVu7i9boYzyb8lbKacoFOhn6jxkSdYulhPtcS2AOKPRhgqm7DkqQKdDrbUk9+Q7QMEBSOXviqXcGDBrbVJ6MEoEWiCUVbxG2rykc/Dr1s5g= 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=P08xVzW6YH+IqAn993xseD49PpIWZrBN6tZibpz9sMpfIwIa2HpO5d5TSvjuE7c8BuGaSompwFvU72yNlgbAVPV2uKYGaGJD7BcSnu+Ca8gZESL4T0HOjCB+UH+uWX4Gp4md3UN+c2Rk216ux0YLiQ7bGrI/tltPeAR5oEaFdGM= Received: by 10.78.176.20 with SMTP id y20mr2376742hue.1182755684389; Mon, 25 Jun 2007 00:14:44 -0700 (PDT) Received: by 10.78.77.16 with HTTP; Mon, 25 Jun 2007 00:14:44 -0700 (PDT) Message-ID: <906dd82e0706250014v599845b5qfa052b861f0a434@mail.gmail.com> Date: Mon, 25 Jun 2007 14:14:44 +0700 From: "Mikhail Loenko" To: dev@harmony.apache.org Subject: Re: [general][M2] Code frozen In-Reply-To: <9623c9a50706250008p7eed94f3w95072c62cca4f060@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: <906dd82e0706240018u3f4f092fqb30fe4aa87b1af03@mail.gmail.com> <6e47b64f0706242359t4a21f1ebu899a5fc5c17dd9f1@mail.gmail.com> <906dd82e0706250004r42911331h64999c8f79518fad@mail.gmail.com> <9623c9a50706250008p7eed94f3w95072c62cca4f060@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org 2007/6/25, Xiao-Feng Li : > On 6/25/07, Mikhail Loenko wrote: > > Let's create snapshots and then decide (based on testing results?) > > what to release > > Why not to have them all? I don't understand. Sorry if I missed It depends on testing results. For example, it does not make much sense to release IPF build as a stable build (IIRC it currently runs apps like "hello world" only) If we have excellent testing results on the first platform and pretty modest ones on the second one (or no testing for the second platform) I'd prefer to release only the first one. Thanks, Mikhail > anything, but I think it's always good to have the choices available, > otherwise the users who want to try will build them anyway. > > Thanks, > xiaofeng > > > Thanks, > > Mikhail > > > > 2007/6/25, Stepan Mishura : > > > On 6/24/07, Mikhail Loenko wrote: > > > > We have passed our code freeze date for M2 > > > > > > > > > > Mikhail, > > > > > > Just to be clear - M1 milestone published snapshots include build for > > > Windows x86, Linux (libstdc++ v5 and libstdc++ v6) x86 and Windows > > > x86_64. > > > > > > I assume that we still aimed to x86 architecture and I need to build > > > milestone candidates for: > > > - Windows x86 > > > - Linux x86. BWT, again for both libstdc++ versions? > > > > > > And what about x86_64? > > > > > > As I said M1 includes Windows x86_64. Should we publish them to let > > > the community test them to see how good they are? > > > > > > Thanks, > > > Stepan. > > > > > > > Last time we executed Tim's policy that each commit should have > > > > approval from two committers, let's follow the same way -- no more > > > > commits please, without agreement from two committers on the dev list. > > > > > > > > Now let's test what we have and see if any critical bugs were > > > > introduced just before the code freeze. Please raise anything you > > > > think is critical/blocker for consideration. > > > > > > > > Thanks, > > > > Mikhail > > > > > > > > > > > > > -- > > > Stepan Mishura > > > Intel Enterprise Solutions Software Division > > > > > > > > -- > http://xiao-feng.blogspot.com >