axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Perry2 <PERR...@uk.ibm.com>
Subject Re: 1.4 looks big !
Date Wed, 03 Nov 2004 08:19:01 GMT




+1 for stability.

Andrew Perry
Clients for Web Service Stack
perryan@uk.ibm.com
Mail Point 127
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828  External + 44 (0)1962 819828
Fax. + 44(0)1962 818080

Samisa Abeysinghe <samisa_abeysinghe@yahoo.com> wrote on 03/11/2004
01:05:40:

> > I agree with John.  I think we need to improve stability and
infastructure
> > prior to adding new features.
>
> +1 for improving stability.
>
> Samisa...
>
> --- Nadir Amra <amra@us.ibm.com> wrote:
>
>
> >
> >
> >
> >
> >
> >
> > John Hawkins <HAWKINSJ@uk.ibm.com>
> > 11/02/2004 07:00 AM
> > Please respond to
> > "Apache AXIS C Developers List"
> >
> >
> > To
> > axis-c-dev@ws.apache.org
> > cc
> >
> > Subject
> > 1.4 looks big !
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Folks,
> >
> > I've just been looking at the WIKI and seen an awful lot of things in
it
> > for 1.4.
> > We (IBM) have some of the items covered. The following are ones I don't
> > know much about ->
> >
> > 3. Improve Fault handling - [AXISCPP-216]
> > 6. Include file refactoring - [AXISCPP-219]
> > 7. Create SSL implementation
> > 10. Improve Makefiles [AXISCPP-221]
> > 11. Prepare tutorial on Handlers and update the Architecture Guide
> > 12. Add href/multiref support [AXISCPP-111]
> > 13. Add Pull parser
> > 15. Implement WS-Attachments
> > 16. Support WS-Scurity & WS-Addressing requirements
> >
> >
> > Assuming that we all agree on producing 1.4 at the end of November then
> > there's an awful lot of work to do here. I'm particularly worried about

> > the
> > size of WS-security & WS-addressing.
> >
> >
> > I have two thoughts with having a large plan -
> > 1. I don't want us to be in the same situation as we were for 1.2 and
1.3
> > of over committing and having to put back our plans. It would be better
to
> > plan fewer things and then be pleasently surprised that we can do more,
> > than overcommitting now?
> >
> > 2. If we put too much into each release then we risk being unstable and
I
> > think that we've still got a lot of problems we can sort out without
> > adding
> > to many new features? We haven't produced a single release yet where
users
> > haven't come back with simple issues.
> >
> > Have we got this contained including the testing - are we being
realistic
> > in saying we can do this for 1.4 or should we reschedule some of these
and
> > try to split some over 1.4 and 1.5 so we improve the quality and
testing?
> >
> > any info or thoughts would be appreciated.
> > thanks,
> > John
> >
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Check out the new Yahoo! Front Page.
> www.yahoo.com
>
>


Mime
View raw message