Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of rickmcg@gmail.com designates
 209.85.216.54 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=V7pCyZQ8HrjpSvtqEEe7c9wapZIXZwx+OR4v+SdimuiTNlsLoMxHUh2bXctkckk/yT
         NHzy9cG5ZkVBWMFo8HVswIJdIZ3F/i4g5tTylA9TFhf+A11QBRQ+XUZ3bJzSIc1jr2W3
         DqveH9zVsxuoeQztys+gE3YD2YMQcGu+/ErAU=
Message-ID: <4CFE8E3F.9020703@gmail.com>
Date: Tue, 07 Dec 2010 14:42:55 -0500
From: Rick McGuire <rickmcg@gmail.com>
Reply-To: rickmcg@gmail.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Geronimo Dev <dev@geronimo.apache.org>
Subject: Creating a 3.0-M2 branch?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm sensing that we might be approaching the point where it might be a 
good idea to create a branch for the 3.0-M2 release.  This would free up 
trunk for any full profile work that might be ready to start as well as 
allowing work to start on eliminating the different snapshot 
dependencies.  Other than fixes for TCK problems, how much work remains 
to be done for 3.0-M2 that should be completed before a branch is 
taken.  I'm thinking we might want to create this branch next week if 
that's feasible.

On a related topic, for the 3.0-M1 release, the source branch was rather 
aggressively pruned of all subprojects that are not in a working state, 
as well as all testsuite tests for those features (e.g., all of the 
webservices components and tests).  That was a fairly time consuming 
process and I'm wondering how much of that needs to be done for the M2 
release.  Less would definitely be better.

Rick