Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
In-Reply-To: <00fa01c4c7bf$99f0c2b0$0665a8c0@dfduc05cq64kja>
Subject: Re: End November Deadline for 1.4
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: 
 <OFE6AA346A.9A764E47-ON80256F49.003178E6-80256F49.004A5206@uk.ibm.com>
From: John Hawkins <HAWKINSJ@uk.ibm.com>
Date: Thu, 11 Nov 2004 13:31:46 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


+1 for release manager !

Thanks for making the plans clear this is a great move :-)

Hmm, there appears to have been a slip from "late November" to early
December. This will have two ramifications:

1. Customers reliant on 1.4 end of November dates. Customers can view date
slippage as very serious. It's a sign that things are being crammed in. We
should avoid date slippage as much as possible. I tried to get the 1.4 and
1.5 plans out in the open way in advance of 1.3 finishing so that we could
discuss the dates and agree them in advance to avoid slipping.

2. C support due in 1.5 - The 1.4 C++ engine work will be ready in time for
late November and we can't really start working on the 1.5 C support until
we have a true 1.4 release. Thus the 1.4 slipping is reducing the 1.5 time
available unless we slip 1.5 (which I'm not happy to do because of point
one :-)

Having said all that. At the moment we (IBM) can afford to slip the
November date but we'd like to see the 1.5 really remain as close to end of
Jan as possible. We (IBM) are going to concentrate on bug fixing and
XML/SOAP support in this period as there are way too many issues in JIRA
for us to be happy with the support levels. Anything we can do to maintain
stability e.g. reduce new function until we are stable would be a great
help ;-)


Other issues - Assuming date is still end of November - We (IBM) can't do
the fault handling work in 1.4. so, unless anyone else can then this is not
in 1.4. The fault handling work is a nice to have I think. The fault
handling is working today so I'm loath to break it now.


thanks for the info - please keep it coming. As long as we communicate on
the list then we'll all be able to understand where we stand and avoid
confusion :-)

speak to you soon,
John.


John Hawkins


             "sanjaya                                                      
             singharage"                                                   
             <sanjayas@opensou                                          To 
             rce.lk>                   "Apache AXIS C Developers List"     
                                       <axis-c-dev@ws.apache.org>          
             11/11/2004 07:25                                           cc 
                                                                           
                                                                   Subject 
             Please respond to         Re: End November Deadline for 1.4   
              "Apache AXIS C                                               
             Developers List"                                              
                                                                           
                                                                           
Hi all,
I would like to volunteer to be the release manager for the Axis C++ 1.4
release.
A draft Release Plan is presented below.


This is the release plan (draft) for Axis C++ version 1.4. Given below is
snapshot
of all the changes for 1.4 since the 1.3 version.

 Changes from 1.3 to 1.4:

1. Create 100% C++ engine - [AXISCPP-206]
2. Refactor WSDL2WS - [AXISCPP-215]
3. Improve Fault handling - [AXISCPP-216]
4. IPV6 - [AXISCPP-217]
5. WSI BP 1.0 compatible - [AXISCPP-218]
6. Include file refactoring - [AXISCPP-219]
7. Create SSL implementation
8. Remove pre-defined paths from Axis CPP Conf library names -
[AXISCPP-220]
9. Eliminate warnings [AXISCPP-155]
10. Improve Makefiles [AXISCPP-221]
11. Prepare tutorial on Handlers and update the Architecture Guide
12. Add Session support [AXISCPP-226]
    Cookie based session support on client side
    SOAP Header based session handling [AXISCPP-238].

13. Implement WS-Attachments (SOAP Messages with Attachments)
14. Support WS-Security & WS-Addressing requirements [AXISCPP-244]
[AXISCPP-212].

Details on these features could be found on JIRA and the AxisCpp TODO wiki
page.

 Release Criteria:

     - Functional tests pass
     - Test on installation procedures
     - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
     - Test samples on different platforms (Linux, Microsoft Windows)
     - Fix  blockers and most critical bugs that applies to 1.4

 Dates:

 The following are the proposed dates for the release, opinions please:
     Code freeze                      November 26, 2004
     Release alpha version        December 03, 2004
     Release beta version         December 08, 2004
     Release 1.4                      December 10, 2004


sanjaya.


----- Original Message -----
From: "Sanjiva Weerawarana" <sanjiva@opensource.lk>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Thursday, November 11, 2004 12:13 PM
Subject: Re: End November Deadline for 1.4


> +1 for having an alpha and beta .. if there are no problems we can
> move from alpha -> beta -> final pretty fast.
>
> Has someone written a release plan for 1.4? That MUST be written
> per Apache rules. Who's going to be release manager?
>
> Sanjiva.
>
> ----- Original Message -----
> From: "sanjaya singharage" <sanjayas@opensource.lk>
> To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> Sent: Thursday, November 11, 2004 11:44 AM
> Subject: Re: End November Deadline for 1.4
>
>
> > Hello John and all,
> >
> > In my opinion the release of an alpha and beta provide the benefit of
the
> > open source model. One trait of an opensource product is that it's code
is
> > read by many, and it is used by many and the problems/issues/bugs
> resulting
> > from that are brought up and addressed. Such use will bring up many a
> > problem that one would not be able to simply think up in my opinion.
Pre
> > releases would help in making the final release stabler and reliable.
> Users
> > would expect a stable and reliable product from a final release from
the
> > fact that is a "final" release. So I think that pre releases do serve
an
> > important role.
> >
> > Thanks,
> > sanjaya.
> >
> > ----- Original Message -----
> > From: "John Hawkins" <HAWKINSJ@uk.ibm.com>
> > To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> > Sent: Wednesday, November 10, 2004 8:07 PM
> > Subject: Re: End November Deadline for 1.4
> >
> >
> > >
> > >
> > >
> > >
> > > Hi Folks,
> > >
> > > There seems to have been some confusion here as to what we mean when
we
> > say
> > > "release". Release to me is when you say the code is ready to go, no
> > > problems (at least no MAJOR problems). Release is not an alpha, or
beta.
> > >
> > > I had assumed when I originally suggested that the 1.4 time schedule
be
> > the
> > > end of November that this was the FINAL release. In fact I had not
> assumed
> > > that we would have an alpha or beta. I don't understand why we need
an
> > > alpha or beta given that these are just point releases.
> > >
> > > As long as the code is being tested on a nightly basis via the
> regression
> > > suite then what else do we need to test for? I understand that there
are
> > > different configurations but I'm sure that between us we can test all
> > these
> > > very quickly in a day?
> > >
> > > Thoughts please?
> > >
> > >
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> > >              Roshan
> > >              Weerasuriya
> > >              <roshan@opensourc
> To
> > >              e.lk>                     Apache AXIS C Developers List
> > >                                        <axis-c-dev@ws.apache.org>
> > >              09/11/2004 09:43
> cc
> > >
> > >
> Subject
> > >              Please respond to         Re: End November Deadline for
1.4
> > >               "Apache AXIS C
> > >              Developers List"
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > yes I do think that is good.
> > >
> > > Roshan
> > >
> > > On Tue, 2004-11-09 at 07:12, Samisa Abeysinghe wrote:
> > > > I think we must think of those who want to use Axis C++ in
production
> > and
> > > help them out as that is
> > > > what make Axis C++ strong.
> > > >
> > > > Samisa...
> > > >
> > > > --- Fred Preston <PRESTONF@uk.ibm.com> wrote:
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >       I would have issues with slipping the 1.4 delivery as we
have
> > > > > customers who are waiting for the cleaner/tidier version of
ws-axis
> at
> > > the
> > > > > end of November.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Fred Preston.
> > > > >
> > > > >
> > > > >
> > > > >
> > >
> > > > >
> > > > >                       damitha@opensourc
> > >
> > > > >
> > > > >                       e.lk                     To:       "Apache
> AXIS
> > C
> > > Developers List"
> > > > > <axis-c-dev@ws.apache.org>
> > > > >                                                cc:
> > >
> > > > >
> > > > >                       08/11/04 10:01           Subject:  Re: End
> > > November Deadline for 1.4
> > > > >
> > > > >                       Please respond to
> > >
> > > > >
> > > > >                       "Apache AXIS C
> > >
> > > > >
> > > > >                       Developers List"
> > >
> > > > >
> > > > >
> > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi Farhaan
> > > > > I too have no issues
> > > > >
> > > > > thanks
> > > > > damitha
> > > > > > hi Farhaan,
> > > > > >
> > > > > > I have no issus on this, but I am not sure about others.
> > > > > >
> > > > > > Roshan
> > > > > >
> > > > > > On Thu, 2004-11-04 at 11:48, Farhaan Mohideen wrote:
> > > > > >> Hi All;
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> Can I assume that 1.4 alpha is to be released by End November
and
> > > not
> > > > > >> the final version. Even delivering alpha is going to be pretty
> > tight
> > > > > >> and I would like to know how you guys feel about the deadline.
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> Regards
> > > > > >>
> > > > > >> Farhaan
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Check out the new Yahoo! Front Page.
> > > > www.yahoo.com
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>