Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <7b774c950706251039s45dc9f7agc6061adefdda0a3f@mail.gmail.com>
Date: Mon, 25 Jun 2007 13:39:06 -0400
From: "Dan Diephouse" <dan@envoisolutions.com>
To: cxf-dev@incubator.apache.org
Subject: Release plan consensus...
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_7150_2753025.1182793146259"

------=_Part_7150_2753025.1182793146259
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think there was some consensus in the previous thread about what to do
with the release process. I think this leaves us with a few takeaways.
warning: some of my own opinions/desires are inter:

1. /trunk is 2.0.1-SNAPSHOT. No destabilizing changes should be made to head
(not going to try to define this - I think its ultimately up to us to make
judgement calls).

2. 2.0.1 should follow about 3-4 weeks from now. I.e. the week of the 16th.

3. Any major changes should be done in a branch for now. I'm not sure if we
should have a 2.1 branch or if we should just have branches for individual
features. I'm guess probably just branches for individual features for now
until 2.0.1 is released, and then we can merge everything into trunk. Though
I think the JAX-WS 2.1, JAXB 2.1, and WS-SX stuff are all intertwined at
least, so that will all need to happen in the same code base.

4. 2.1 Should probably happen as soon as we finish TCK testing. That should
give anyone ample time to get new features in if they want. Any features
which don't make it can go into 2.2, which should hopefully follow 8-10
weeks after.

Thoughts?

- Dan

-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

------=_Part_7150_2753025.1182793146259--