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)
Message-ID: <20041007054129.87788.qmail@web40628.mail.yahoo.com>
Date: Wed, 6 Oct 2004 22:41:29 -0700 (PDT)
From: Samisa Abeysinghe <samisa_abeysinghe@yahoo.com>
Subject: Re: Code freeze for Axis C++ 1.3 final release.
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
In-Reply-To: <00a901c4ac29$ed3ef7e0$0665a8c0@dfduc05cq64kja>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

The point is simple. Old transport has known critical bugs (such as message size limits and
terribly slow). New transport has proven to solve the problems and fast as well. Hence it is not a
question of different transports for 1.3 beta and 1.3 final. Rather a question of fixing known
bugs in 1.3 beta in 1.3 final.

Is it a good idea to ship a buggy transport with 1.3 fianl, while we have the solution in the CVS
already?

Samisa...

--- sanjaya singharage <sanjayas@opensource.lk> wrote:

> Is it wise to change the tranport in the middle of the release? To
> elaborate, the 1.3 Alpha and Beta will have one transport and the final
> release will have a different  new transport. Is this recommended or ok
> practise for apache projects?
> 
> sanjaya.
> 
> ----- Original Message -----
> From: "Samisa Abeysinghe" <samisa_abeysinghe@yahoo.com>
> To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
> Sent: Wednesday, October 06, 2004 4:56 PM
> Subject: Re: Code freeze for Axis C++ 1.3 final release.
> 
> 
> > Are we making axis2 transport and Xerces based paser lib as defaults for
> 1.3 final release?
> > If yes, we have to change the docs accordingly.
> > If no, why not ;-)
> >
> > Thanks,
> > Samisa...
> >
> > --- damitha kumarage <damitha@opensource.lk> wrote:
> >
> > > Hi all,
> > >
> > > How about freezing the Axis C++ code base in preparation for  1.3 final
> > > Release on 07th October 2004 and making a final release on 08th October
> > > 2004.
> > > During this period developers are expected to adhere to the following.
> > >
> > > * There will be no new addition to the existing code in the CVS.
> > >    That means no new feature added or existing feature removed.
> > >
> > > * Folders/Files/Classes/Variables/Methods  will not be added or removed
> > >    unless it is required by bug fixes.
> > >
> > > * Only bug fixes are allowed which are recorded in Jira. But prior to
> > > the fix the developer needs to send a notice to the C dev mailing list
> > > explaining his move. Before fixing the bug tagging the cvs with a
> > > meaningful name is recommended
> > >
> > >
> > > regds
> > > damitha
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > _______________________________
> > Do you Yahoo!?
> > Declare Yourself - Register online to vote today!
> > http://vote.yahoo.com
> >
> >
> 
> 
> 


__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail