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.168 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=PWFAijn1SruGjkStiyaUcxC6ilOJq7yxhI5MvFtKiI9c4vrT4IMo04+Xi0rQXGPjUMRwVDmS48x4GryNeBUieNmvqwxAG6xEJea0YcHYuHANNOqJ0fflLCDSgCDd8AGddHb3oYWVqeE8NxTUj1AoVx9TBsL6PXFpW1UBZ/efKAM=
Message-ID: <46E9032D.5090703@gmail.com>
Date: Thu, 13 Sep 2007 10:30:21 +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 schedule
References: <6e47b64f0709130051x2bbfe91ew3891665a51ca3051@mail.gmail.com>
In-Reply-To: <6e47b64f0709130051x2bbfe91ew3891665a51ca3051@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Stepan, thanks for bringing this up again.

Stepan Mishura wrote:
> OK, at least nobody suggested that we have longer then 3-month
> schedule. That means that we should have next milestone no later then
> September, 30.

Agreed, let's shoot for the end of the month for M3.

> So I'd like to remind that we are close to the mid of September and
> propose the following M3 schedule:
> - Septemer 15: feature freeze - svn trunk is frozen
> I think this time it makes sense to freeze the trunk instead of
> branching to avoid doing merges for bugfixes

Yep, so no new areas of significant functionality should be introduced
after Sept 15th; but we can continue to do bug/perf/tidy-up type changes
during this period.

> - Septemer 22: code freeze - M3 branch(tag?) is created and the trunk
> is unfrozen. All fixes for M3 go to the branch.

So what are you proposing gets branched? everything (and only those
things) that contributes to the federated build? e.g. drlvm, classlib,
and jdktools.  I assume that the BTI code is not branched too?

Can BTI and other scripts cope ok with switching to the code on a branch
rather than dealing with HEAD?

Once the M3 branch is created then I assume that the HEAD is opened once
again for code and feature changes, but changes to the stable M3 branch
require our established `review then commit` style.

> - Septemer 29 :release date - M3-branch is merged with the trunk.

Though there is no reason why we would not merge the M3 branch into HEAD
during the M3-shut-down period either, right?  At the end of Sept we do
the final merge, then delete the M3 branch.

> Objections?

No, I'm keen that we get another stable build published.

Regards,
Tim