Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 15135 invoked from network); 22 Aug 2007 10:39:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2007 10:39:28 -0000 Received: (qmail 84074 invoked by uid 500); 22 Aug 2007 10:39:25 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 83531 invoked by uid 500); 22 Aug 2007 10:39:23 -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 83522 invoked by uid 99); 22 Aug 2007 10:39:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 03:39:23 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of t.p.ellison@gmail.com designates 64.233.182.187 as permitted sender) Received: from [64.233.182.187] (HELO nf-out-0910.google.com) (64.233.182.187) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 10:39:57 +0000 Received: by nf-out-0910.google.com with SMTP id k4so94871nfd for ; Wed, 22 Aug 2007 03:39:00 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=lgl2lx1eYsliwTmWbPGiK5HxksxJ/MWDw+C34aIpEAqn7SVWE1zz15EE7qA/g/3L6Vf7QlJ/F62nfl/fAnT11oifrgz3DtuNoQq5V3H6GbxhhOcJjjrEGGb+md7pema947nUr0zQp/MpZZGl4du6UuWwZZx5tTtC6/iQ6JK4W8U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=NA/h8GC2SYrcjdAmOa1P4ZNm4bQQiHwWOVazYlaWsJtYL7qQfAxUTiqu5idJeq0SBcv52sO1rpbcB6q3zTKRb5Ag93W8lW758VjFcs4lLwSthHxSRuagWwjAmOVgU0DP4sRlVBMvXM9kR+yQaBvmfRlSLHvrCTRz0/O1mzztN/U= Received: by 10.86.28.5 with SMTP id b5mr406672fgb.1187779139996; Wed, 22 Aug 2007 03:38:59 -0700 (PDT) Received: from ?192.168.0.2? ( [86.111.176.100]) by mx.google.com with ESMTPS id c22sm1068412ika.2007.08.22.03.38.51 (version=SSLv3 cipher=RC4-MD5); Wed, 22 Aug 2007 03:38:52 -0700 (PDT) Message-ID: <46CC1238.1020702@gmail.com> Date: Wed, 22 Aug 2007 11:38:48 +0100 From: Tim Ellison User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: dev@harmony.apache.org Subject: Re: [general] M3 milestone discussion References: <6e47b64f0708120602q1e9a9c7fvf786b64a4d3ee991@mail.gmail.com> <4dd1f3f00708121935m4b8ef591i9492d0242db432e5@mail.gmail.com> <46CB4BF7.8020107@gmail.com> <906dd82e0708212116y688ab795odff3df2df9fa1b02@mail.gmail.com> <6e47b64f0708220135u56d4a8e8q66116b21bcaa11a8@mail.gmail.com> In-Reply-To: <6e47b64f0708220135u56d4a8e8q66116b21bcaa11a8@mail.gmail.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Stepan Mishura wrote: > On 8/22/07, Mikhail Loenko wrote: >> Basing on M2 experience I think 2-mo is a too short for Harmony: >> 25% of the whole time we would have our workspace somehow frozen. >> And we couldn't shorten freeze time since we have long running >> suites and scenarios. >> >> IMHO it negatively affects progress of the project. >> So I'm +1 for having fixed schedule, but 2-mo schedule does not leave >> enough time for normal development > > I agree with Mikhail - 2 month schedule looks too short. Why? How long should we go before checking stability is maintained? I see lots of work going on daily, things look good from here. Regards, Tim