Return-Path: 
 <dev-return-32002-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org>
Delivered-To: apmail-harmony-dev-archive@www.apache.org
Received: (qmail 97438 invoked from network); 10 Feb 2008 21:59:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 10 Feb 2008 21:59:53 -0000
Received: (qmail 33224 invoked by uid 500); 10 Feb 2008 21:59:45 -0000
Delivered-To: apmail-harmony-dev-archive@harmony.apache.org
Received: (qmail 33200 invoked by uid 500); 10 Feb 2008 21:59:44 -0000
Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@harmony.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@harmony.apache.org>
List-Post: <mailto:dev@harmony.apache.org>
List-Id: <dev.harmony.apache.org>
Reply-To: dev@harmony.apache.org
Delivered-To: mailing list dev@harmony.apache.org
Received: (qmail 33191 invoked by uid 99); 10 Feb 2008 21:59:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 13:59:44 -0800
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 t.p.ellison@gmail.com
 designates 66.249.92.172 as permitted sender)
Received: from [66.249.92.172] (HELO ug-out-1314.google.com) (66.249.92.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Feb 2008 21:59:13 +0000
Received: by ug-out-1314.google.com with SMTP id u40so186337ugc.3
        for <dev@harmony.apache.org>; Sun, 10 Feb 2008 13:59:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        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;
        bh=KUvFQMyF9bMxDXHVIe5xwfW/Iw7UE1ckkaT3iujnGyU=;
        b=vXEavWQK3poE0W2Qvub1FUwviLgdrhqUrRiGsZqs275+ybgE+VJHNlq9e6eL33U8hookIhS/Jey/qGflnwm8tHkee5VBuzxExSt79T8DmABTQgQOw2yC3qfMLD6f4RUfZrqTuWtGIiqjod/DQdz/zdrRj/gkbVwwnifueDtvXtc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=q9oRnJBre+mWHPkxo1bKk0q8I/DPElXlWXX2BS/5l9EK60F1lX/Fa2TIU7hz4sZ4fnOdEuFQ954xXUNdfQeZcS5hwyc3TPOUncpW3vtTA0zgthqEXWlr8bnQgmsJJnCu+c+4C5KH9+2q7H18zUMOeAUe7gtzestcMU/EOHuuQOc=
Received: by 10.67.19.17 with SMTP id w17mr8284047ugi.33.1202680760306;
        Sun, 10 Feb 2008 13:59:20 -0800 (PST)
Received: from ?192.168.0.5? ( [86.111.176.100])
        by mx.google.com with ESMTPS id 24sm5580582ugf.22.2008.02.10.13.59.18
        (version=SSLv3 cipher=RC4-MD5);
        Sun, 10 Feb 2008 13:59:18 -0800 (PST)
Message-ID: <47AF73B3.6020705@gmail.com>
Date: Sun, 10 Feb 2008 21:59:15 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [milestone] Thoughts for M5
References: <47A7057D.3000803@gmail.com>
 <c3755b3a0802050345n6c040255p68932a25c8c6955a@mail.gmail.com>
In-Reply-To: <c3755b3a0802050345n6c040255p68932a25c8c6955a@mail.gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

I didn't hear any objections (or a lot of support for that matter <g>) 
so let's go with Feb 22 as our target date for Milestone 5.

That means code freeze on Fri Feb 15th and no new features from now on.
If there are problems with those dates speak-up *now* -- we can shift 
everything later by a week with no great repercussion.

I'll be away from the keyboard for the last week up to M5, but I'm sure 
you won't notice.

Regards,
Tim

Alexey Petrenko wrote:
> No objections.
> Let's create list of must-fix issues.
> 
> SY, Alexey
> 
> 2008/2/4, Tim Ellison <t.p.ellison@gmail.com>:
>> As usual, we are all busy putting in new functionality and addressing
>> bugs in the latest HEAD stream.  Let's not forget delivering that
>> goodness those users who move from milestone to milestone release.
>>
>> We are getting into the habit now of producing stable, well-tested
>> milestone builds; and this would be Milestone 5.
>>
>> How about we aim for Fri February 22nd for the next stable release, with
>> our usual feature and code chill-down periods?
>>
>> Regards,
>> Tim
>>
>