Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of t.p.ellison@gmail.com
 designates 66.249.92.174 as permitted sender)
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=W/qmkwyH2NeeyblNwePlY0TvZo0/w8aAMDItoUEoZybSNFI03f8+p84mNHMu/jStX5q9TXe4Tg0kgz/13YXO6Emo2zOUA6lmFAyJaJqRyy/eOXnle0h/mBE9CiH2ToExpeLU883TXKSvidhJiIfrkMjqr8C4QW4Kv7Xu+jJGg4c=
Message-ID: <46F586B6.3060305@gmail.com>
Date: Sat, 22 Sep 2007 22:18:46 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [general] M3 - code frozen
References: <6e47b64f0709220918q66644708m7dbc82ac58a9ecb4@mail.gmail.com>
In-Reply-To: <6e47b64f0709220918q66644708m7dbc82ac58a9ecb4@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Stepan Mishura wrote:
> According to the plan - Sept. 22 is code freeze date for M3 so let's
> follow policy:
> "no more commits please without agreement from two committers on the dev list."
> 
> Let's do more testing and analyze if there any critical/blocker issues
> for consideration.
> Please raise here issues that you think MUST be fixed for M3.

Agreed, thanks for the reminder.  The focus moves onto testing what we
have got, and raising any regressions or bugs that seriously inhibit
areas of functionality.  The goal is a stable build at the end of the month.

A MUST fix is removing the IDEA algorithm from the version of
BouncyCastle that we redistribute -- see HARMONY-4810.

Shall we track these with an umbrella JIRA issue?

As part of the code freeze, I'm going to resync the Java 6 branch.

Regards,
Tim