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: <20041029011201.71307.qmail@web40623.mail.yahoo.com>
Date: Thu, 28 Oct 2004 18:12:01 -0700 (PDT)
From: Samisa Abeysinghe <samisa_abeysinghe@yahoo.com>
Subject: Re: 1.3 Bug fix branch
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
In-Reply-To: <1151.220.247.250.52.1098968920.squirrel@220.247.250.52>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hi Damitha,
Could you please help us create one and let us know how to commit to the specific branch.
Thanks,
Samisa...

--- damitha@opensource.lk wrote:

> Hi Samisa,
> I think It is standard procedure to maitain a bugfix branch for a major
> release so the users can update with latest bug fixes.
> We definitely need a bug fix branch because the cvs head is going under
> lot of changes at this time.
> 
> thanks
> damitha
>  Hi All,
> >    I have been fixing few bugs, one related to C support and another to
> > new transport, that is
> > there in 1.3 final and commited to CVS head.
> >    However users would not be able to use them effectively with current
> > CVS as there are major
> > changes going on, with headers etc.
> >    I guess it would be useful to have a bug fix branch for 1.3 in case
> > users need critical fixes
> > and do a 1.3.1 release later on till 1.5 comes up with C support.
> >
> >     However, are we willing to bare the burden of maintaining 2 branches?
> >     Thoughts please.
> >
> > Thanks,
> > Samisa...
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Address AutoComplete - You start. We finish.
> > http://promotions.yahoo.com/new_mail
> >
> >
> 
> 


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