Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <464B0C9A.1050208@thoughtcraft.com>
Date: Wed, 16 May 2007 09:52:26 -0400
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: Skipping 1.2.1 (Re: [Axis2] What's next - 1.2.1 or 1.3?)
References: <19e0530f0705150943ybd841e6p7334deccc0c1b66@mail.gmail.com>	
	<9b85c45f0705152328r65cb8d63u7ca0dde82f6c84a1@mail.gmail.com>
	<9abd5e730705160011r2508aed4v6140e234dd41a312@mail.gmail.com>
	<464ABDAA.1040308@opensource.lk>
In-Reply-To: <464ABDAA.1040308@opensource.lk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From: Glen Daniels <glen@thoughtcraft.com>

My $0.02:

* If there is indeed a list of quick, critical fixes, then those can and 
should be fixed and we should do a 1.2.1 release from the 1.2 branch. 
I'm +1 for this as long as we're careful about the next point.

* Anything that gets fixed on the 1.2 branch should also be fixed on the 
trunk, if it's not already.  Ideally the fix should actually happen in 
the trunk and be merged over to the branch where possible.

* The trunk should keep moving forward, working towards 1.3 in the 
relatively near future regardless.  We should start collecting 
line-items for what we'd like to see by the time 1.3 goes out.

Thanks,
--Glen

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org