Abeysinghe [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 21, 2005 3:44 AM
To: Apache AXIS C Developers List
Subject: Re: Proposal - release versioning and branching model.
It is unfair for you to aks me to stop the thread after you went on
extending this.
It is still unfair on the part of deve
or this discussion thread.
>
> thanks
> -Lilantha
>
> -Original Message-
> From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 21, 2005 3:44 AM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching
ore.
Thanks others for been so patient on for this discussion thread.
thanks
-Lilantha
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, January 21, 2005 3:44 AM
To: Apache AXIS C Developers List
Subject: Re: Proposal - release versioning and branching mode
ilto:[EMAIL PROTECTED]
> Sent: Friday, January 21, 2005 2:49 AM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching model.
>
> Well there is a right time for everything. While there are *more
> important things* like fixing Jira issues are pen
top this thread here with a JIRA entry for this to be discuss
later.
-L
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, January 21, 2005 2:49 AM
To: Apache AXIS C Developers List
Subject: Re: Proposal - release versioning and branching model.
Well t
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 21, 2005 2:07 AM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching model.
>
> On Fri, 21 Jan 2005 01:42:15 -0500, Lilantha Darshana
> <[EMAIL PROTECTED]> wrot
majority VOTE.
-L
-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, January 21, 2005 2:07 AM
To: Apache AXIS C Developers List
Subject: Re: Proposal - release versioning and branching model.
On Fri, 21 Jan 2005 01:42:15 -0500, Lilantha Darshana
<[EM
now.
>
> Samisa...
>
> >
> > -L
> >
> >
> > -Original Message-
> > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 20, 2005 11:53 PM
> > To: Apache AXIS C Developers List
> > Subject: Re: Proposal - rel
ot now.
Samisa...
>
> -L
>
>
> -Original Message-
> From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 20, 2005 11:53 PM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching model.
>
> I st
ent: Thursday, January 20, 2005 9:18 PM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching model.
>
> > Ahh... In which version would you think we should put these 100+ defects
> > fixes? :-)
>
> The next, that is 1.5 ofcour
9:18 PM
> To: Apache AXIS C Developers List
> Subject: Re: Proposal - release versioning and branching model.
>
> > Ahh... In which version would you think we should put these 100+ defects
> > fixes? :-)
>
> The next, that is 1.5 ofcource.
> Provided we have enough hand
Sent: Thursday, January 20, 2005 9:18 PM
To: Apache AXIS C Developers List
Subject: Re: Proposal - release versioning and branching model.
> Ahh... In which version would you think we should put these 100+ defects
> fixes? :-)
The next, that is 1.5 ofcource.
Provided we have enough hands
> Ahh... In which version would you think we should put these 100+ defects
> fixes? :-)
The next, that is 1.5 ofcource.
Provided we have enough hands fixing them, given that current active
developrs are fixing as much as they can and are fully occupied doing
the same.
Samisa...
Samisa Abeysinghe wrote:
>As far as version numbering goes, well I just dont feel its the right
>time to discuss this - there are better things to do - like fixing
>100+ issues in Jira :)
>
>
Ahh... In which version would you think we should put these 100+ defects fixes?
:-)
>Anyway, we cannot
or optimizations
> > that do not introduce new features.
> > Developers may perform a point release if the release is at least
> > interface-compatible with the previous
> > release. In other words, whenever a client depends upon a component
> > with a given point release,
e, it
> will work with all subsequent point releases within that minor release
>
> Additionally we shall have alpha, beta, rc versions as currently we
have.
>
>
> I haven't heard from others, please provide your thoughts & suggestions?
> regards,
> -Lilantha
>
small typo correction see below (i.e. 1.4 should be
1.b)
regards, -Lilantha
-Original Message-From: Lilantha Darshana
[mailto:[EMAIL PROTECTED]Sent: Wednesday, January 19, 2005 3:22
PMTo: Apache AXIS C Developers ListSubject: RE: Proposal -
release versioning and branching model
to"Apache AXIS C Developers
List"
To
"axis \(E-mail\)"
cc
Subject
Proposal - release
versioning and branching model.
+1 for supporting this version numbering system.
Susantha.
Lilantha Darshana wrote:
Proposal - release versioning and branching model.
Hi All,
I was thinking about the maturity
scale of the Axis C++ compare to axis java and others.
It seems like we move very fast in our
11
Please respond to
"Apache AXIS C Developers List"
To
"axis \(E-mail\)"
cc
Subject
Proposal - release versioning
and branching model.
Hi All,
I was thinking about the maturity scale
of the Axis C++ compare to axis java and others.
It seems like we move ve
Title: Proposal - release versioning and branching model.
Hi All,
I was thinking about the maturity scale of the Axis C++ compare to axis java and others.
It seems like we move very fast in our release versioning and does not make much
progress on the maturity scale of the project. Now
21 matches
Mail list logo
