Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 13505 invoked from network); 30 Mar 2005 10:01:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Mar 2005 10:01:47 -0000 Received: (qmail 80647 invoked by uid 500); 30 Mar 2005 10:01:47 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 80628 invoked by uid 500); 30 Mar 2005 10:01:47 -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 80614 invoked by uid 99); 30 Mar 2005 10:01:47 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DATE_IN_FUTURE_03_06,FORGED_RCVD_HELO,RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from illhyd-static-203.200.208.232.vsnl.net.in (HELO smtp.virtusa.co.in) (203.200.208.232) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 30 Mar 2005 02:01:44 -0800 Received: from HS-MAILSVR.Virtusa.com ([10.4.10.60]) by smtp.virtusa.co.in with InterScan Messaging Security Suite; Wed, 30 Mar 2005 15:28:09 +0530 Received: from ws-mailsvr.Virtusa.com ([10.3.8.4]) by HS-MAILSVR.Virtusa.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 30 Mar 2005 15:33:53 +0530 Received: from ws-mailhost.virtusa.com ([172.16.1.6]) by ws-mailsvr.Virtusa.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 30 Mar 2005 05:01:19 -0500 Received: from cs-mailsvr.Virtusa.com ([10.2.1.11]) by ws-mailhost.virtusa.com with InterScan Messaging Security Suite; Wed, 30 Mar 2005 05:02:23 -0500 Received: from 10.2.6.153 ([10.2.6.153]) by cs-mailsvr.Virtusa.com ([10.2.1.11]) with Microsoft Exchange Server HTTP-DAV ; Wed, 30 Mar 2005 10:00:26 +0000 Received: from Samisa by 10.2.1.11; 30 Mar 2005 15:56:34 +0000 Subject: RE: 1.5 Release and codefreeze From: Samisa Abeysinghe To: Apache AXIS C Developers List In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Organization: Virtusa Corporation Message-Id: <1112197800.2724.16.camel@Samisa> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 30 Mar 2005 15:56:34 +0000 X-OriginalArrivalTime: 30 Mar 2005 10:01:19.0559 (UTC) FILETIME=[6B944D70:01C5350F] X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I have been able to fix the garbage return problem for server side generated code. We are seeing some server side problems in case of IHeadeBlock tests and IAttribute tests. This we hope will be able to solve soon. We are in good shape to freeze the code now - Sanjaya, I think we should be tagging the CVS for code freeze by EOD today or tomorrow morning. Thoughts please. Thanks, Samisa... On Wed, 2005-03-30 at 08:10, John Hawkins wrote: > Please be aware that we are not running the client tests for the next > few days so cannot help on whether the client is good or not on all > platforms. >=20 >=20 >=20 >=20 > "Samisa Abeysinghe" > >=20 > 30/03/2005 04:20 > Please respond to > "Apache AXIS C Developers List" > To > "Apache AXIS C > Developers List" > > cc >=20 > Subject > RE: 1.5 Release > and codefreeze >=20 >=20 >=20 >=20 > We have one critical issue on the server side, where the server > returns garbage at some instances. I am looking into this. >=20 > Other than that, tests with C++ server side are looking good. >=20 > =20 >=20 > Thanks, >=20 > Samisa=E2=80=A6 >=20 > =20 >=20 > -----Original Message----- > From: John Hawkins [mailto:hawkinsj@uk.ibm.com]=20 > Sent: Tuesday, March 29, 2005 9:58 PM > To: Apache AXIS C Developers List > Subject: Re: 1.5 Release and codefreeze >=20 > =20 >=20 >=20 > Hi Sanjaya,=20 >=20 > I was just wondering this myself today ! >=20 > Code-freeze should be when we get a build that passes 100% of the test > cases? We've currently got a few failing that I believe samisa was > looking at? >=20 > What will happen between codefreeze and release date will dictate the > time frame won't it? >=20 >=20 >=20 >=20 >=20 >=20 >=20 > "sanjaya singharage" > >=20 > 29/03/2005 13:59 >=20 >=20 > Please respond to > "Apache AXIS C Developers List" >=20 > To > "Apache AXIS C > Developers List" > > cc > =20 > Subject > 1.5 Release and > codefreeze >=20 > =20 >=20 >=20 > =20 > =20 >=20 >=20 >=20 >=20 > Can we decide on a date for codefreeze for the 1.5 final release? >=20 > And a release date as well. >=20 > Also if there are outstanding issues could we list them out so that we > can > systematically attend to them? >=20 > sanjaya. >=20 --=20 Samisa Abeysinghe Virtusa Corporation