axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject Re: Why are we releasing?
Date Thu, 07 Oct 2004 11:54:07 GMT
Yes it is a good idea to switch to new transport.

I think Damitha has already put it in the build for Linux.

Samisa...

--- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:

> 
> 
> 
> 
> And I assume that as we are effectively regressing that we are going to use
> the new transport?
> 
> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              07/10/2004 12:17          <axis-c-dev@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           Re: Why are we releasing?           
>              Developers List"                                              
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> > Mark Whitlock is going to look into AxisCPP 192 and then 193 (Adrian
> Smiths
> > problems). These issues would appear to be quite generic and fundamental.
> 
> Great.
> 
> > Samisa - would you like to prioritise?
> 
> Sure I would love to.
> AXISCPP-171 - Axis bench and Xerces buffers (already looked into some
> detail. still looking into
> buffer zise implications)
> AXISCPP-89  - Messages larger than 2048 fails (need to test on Windows)
> 
> AXISCPP-184 - < and > in strings (Not sure if high priority)
> 
> And some doc stuff.
> 
> Thanks,
> Samisa...
> 
> 
> 
> --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
> 
> >
> >
> >
> >
> > OK, so this sounds positive,
> >
> > Providing there are no dissenters - Let's work out what issues we are
> going
> > to tackle.
> >
> > Mark Whitlock is going to look into AxisCPP 192 and then 193 (Adrian
> Smiths
> > problems). These issues would appear to be quite generic and fundamental.
> 
> Great.
> 
> >
> > Then we have to list what other ones we are going to fix before we start
> > talking about a release.
> >
> > Samisa - would you like to prioritise?
> >
> >
> >
> >
> >
> >
> > John Hawkins
> >
> >
> >
> >
> >
> 
> >              "sanjaya
> 
> >              singharage"
> 
> >              <sanjayas@opensou
> To
> >              rce.lk>                   "Apache AXIS C Developers List"
> 
> >                                        <axis-c-dev@ws.apache.org>
> 
> >              07/10/2004 11:40
> cc
> >
> 
> >
> Subject
> >              Please respond to         Re: Why are we releasing?
> 
> >               "Apache AXIS C
> 
> >              Developers List"
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> >
> >
> >
> > sounds logical to me.
> >
> > sanjaya.
> >
> > ----- Original Message -----
> > From: "John Hawkins" <HAWKINSJ@uk.ibm.com>
> > To: <axis-c-dev@ws.apache.org>
> > Sent: Thursday, October 07, 2004 4:06 PM
> > Subject: Why are we releasing?
> >
> >
> > >
> > >
> > >
> > >
> > > Hi Folks,
> > >
> > > It appears to me that we are being premature in releasing this code.
> > >
> > > We have fundamental issues with the transport and we have major bugs as
> > > seen by adrian Smith (and many more on JIRA)
> > >
> > > I would propose that we ascertain the resolutions to these major issues
> > > before we say that we are releasing? I would propose that all "Major"
> > bugs
> > > be fixed prior to declaring a release.
> > >
> > > If we release another drop with these large bugs in it then we simply
> put
> > > off people from using the code and they won't trust us.
> > >
> > >
> > >
> > >
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
> 
> 
> 



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

Mime
View raw message