Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 11959 invoked from network); 1 Mar 2006 12:01:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Mar 2006 12:01:46 -0000 Received: (qmail 40175 invoked by uid 500); 1 Mar 2006 12:02:10 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 40117 invoked by uid 500); 1 Mar 2006 12:02:10 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 40054 invoked by uid 99); 1 Mar 2006 12:02:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2006 04:02:10 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [12.40.51.197] (HELO mailhost.virtusa.com) (12.40.51.197) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2006 04:02:09 -0800 Received: from cs-mailsvr.Virtusa.com ([10.2.1.11]unverified) by mailhost.virtusa.com with InterScan Messaging Security Suite; Wed, 01 Mar 2006 06:58:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C63D27.E383BE9E" Subject: RE: Proposal : Time to release Axis C++ 1.6beta Date: Wed, 1 Mar 2006 18:01:43 +0600 Message-ID: <785A212E11918F449D1318C61B7A9B0E03502A25@cs-mailsvr.Virtusa.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Proposal : Time to release Axis C++ 1.6beta Thread-Index: AcY9JyT5MLsEgmkET3i7wR/lurF4rwAAJmXw From: "Chinthana C. Dinapala" To: "Apache AXIS C Developers List" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C63D27.E383BE9E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable +1 From me. =20 Chinthana Dinapala Virtusa Corp.=20 =20 ________________________________ From: Paul Fremantle [mailto:pzfreo@gmail.com]=20 Sent: Wednesday, March 01, 2006 5:56 PM To: Apache AXIS C Developers List Subject: Re: Proposal : Time to release Axis C++ 1.6beta =20 +1 from me Adrian. Great work. Paul On 3/1/06, Manohar K Chintala wrote:=20 +1 Regards Manohar Adrian Dick < adrian.dick@uk.i =20 bm.com> To axis-c-dev@ws.apache.org=20 03/01/2006 03:03 cc PM =20 Subject Proposal : Time to release Axis C++=20 Please respond to 1.6beta "Apache AXIS C Developers List" (This is a repeat send, because I can't find any evidence of the original=20 getting through the system - apologies if you receive this twice) Hi, Guys, I wish to propose we produce an Axis C++ 1.6 beta, and if no significant problems are found we should release the 1.6 final two weeks later.=20 Here is my reasoning behind this proposal: In the past few weeks, a lot of the issues we've been seeing on the mailing list have already been fixed in the latest nightly builds. It would therefore be a good time to consider releasing, particularly as it has been=20 over 10 months since any form of release. 254 Jira issues have been fixed since the 1.5 final release. But this isn't just a fix release, there has also been an increase in capability added to the Axis C++ engine and the WSDL2Ws tooling:=20 Improvements within the engine include: memory management transport layer cookie support addition of Configuration API Improved WSDL support for: xsd built-in simple types (all types now supported)=20 xsd:any xsd:choice xsd:all The nightly builds when tested today on Windows, Linux and AIX have only 1 client testcase failing (see AXISCPP-942) from 288 attempted. It looks like AXISCPP-942 should be fixed very soon, but I feel we can=20 still try producing a beta, and ensure this fix gets into the final release. Regards, Adrian _______________________________________ Adrian Dick (adrian.dick@uk.ibm.com ) --=20 Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle=20 paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com ------_=_NextPart_001_01C63D27.E383BE9E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

+1 From = me.

 

Chinthana Dinapala

Virtusa<= /font> Corp. =

 

=

From: Paul = Fremantle [mailto:pzfreo@gmail.com]
Sent: Wednesday, March = 01, 2006 5:56 PM
To: Apache AXIS C = Developers List
Subject: Re: Proposal : = Time to release Axis C++ 1.6beta

 

+1 from me = Adrian. Great work.

Paul

On 3/1/06, Manohar K Chintala <cmanohar@in.ibm.com> wrote:

+1

Regards
Manohar



             = Adrian Dick
             = < adrian.dick@uk.i
             = bm.com>      =             &= nbsp;           &n= bsp;           &nb= sp;         To
            &= nbsp;           &n= bsp;           &nb= sp;  axis-c-dev@ws.apache.org =
             03/01/2006 03:03           &n= bsp;           &nb= sp;           &nbs= p;       cc
             = PM
            &= nbsp;           &n= bsp;           &nb= sp;           &nbs= p;            = ;      Subject
            &= nbsp;           &n= bsp;           &nb= sp;  Proposal : Time to release Axis C++
             = Please respond to         1.6beta
            &= nbsp; "Apache AXIS C
             Developers List"








(This is a repeat send, because I can't find any evidence of the = original
getting through the system - apologies if you receive this twice)

Hi, Guys,

I wish to propose we produce an Axis C++ 1.6 beta, and if no = significant
problems are found we should release the 1.6 final two weeks later.


Here is my reasoning behind this proposal:

In the past few weeks, a lot of the issues we've been seeing on the = mailing
list have already been fixed in the latest nightly builds.  It = would
therefore be a good time to consider releasing, particularly as it has = been
over 10 months since any form of release.

254 Jira issues have been fixed since the 1.5 final release.

But this isn't just a fix release, there has also been an increase = in
capability added to the Axis C++ engine and the WSDL2Ws tooling:
Improvements within the engine include:
   memory management
   transport layer
   cookie support
   addition of Configuration API

Improved WSDL support for:
   xsd built-in simple types (all types now supported)
   xsd:any
   xsd:choice
   xsd:all


The nightly builds when tested today on Windows, Linux and AIX have only = 1
client testcase failing (see AXISCPP-942) from 288 attempted.
It looks like AXISCPP-942 should be fixed very soon, but I feel we can =
still try producing a beta, and ensure this fix gets into the final
release.

Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com )





--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blo= g/paulfremantle
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

------_=_NextPart_001_01C63D27.E383BE9E--