Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 5303 invoked from network); 19 Dec 2007 05:03:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Dec 2007 05:03:19 -0000 Received: (qmail 76154 invoked by uid 500); 19 Dec 2007 05:03:06 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 76107 invoked by uid 500); 19 Dec 2007 05:03:05 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 76096 invoked by uid 99); 19 Dec 2007 05:03:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2007 21:03:05 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.9] (HELO relay00.pair.com) (209.68.5.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 19 Dec 2007 05:02:44 +0000 Received: (qmail 91052 invoked from network); 19 Dec 2007 05:02:45 -0000 Received: from unknown (HELO ?127.0.0.1?) (unknown) by unknown with SMTP; 19 Dec 2007 05:02:45 -0000 X-pair-Authenticated: 123.231.21.16 Message-ID: <4768A5EE.3000002@opensource.lk> Date: Wed, 19 Dec 2007 10:32:38 +0530 From: Deepal Jayasinghe User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: "axis-dev@ws.apache.org" , "axis-user@ws.apache.org" Subject: [Axis2] Release plan and road map for Axis2 1.4 release X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Devs and Users, I saw a number of users asking about the next release of Axis2 , so I think its good time to think about that. We did our last release on August , looking at the mailing list and JIRA I can assume that the release is very stable release. However in the meantime we have few items that we need to implement that we discussed over the mailing list for the next release. And there are a few bug fixes and new features that users have ask about , so taking all those into account how about doing a release on end of February ? So in the release I would like to see following list of items - Support for RPC-Encoded - Full support for JAX-WS - Enhance NIO transport support - Discuss and implement dynamic phase rule support - Fix the issues we found at MS PlugFest - Anything else ..... ?? In addition to that we need to identify the issues that we are going to fix in next release , for that I would like ask Axis2 users to go and create a JIRA or change the priority of JIRA if they want some issues or features (s)he like to see in next release. In the meantime if someone think to fix some particular issue for next release then please go and mark the issue as blocker. But please do not just mark issue as blocker provide some useful information specifying what do you think its is important. So let's target Axis2 1.4 on end of February , and here is my +1 for the release. -Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org