I think you have misunderstood this, and going in an unnecessary discussion. and wasting your valuable time that you can spend on defect fixes. don't worry, as time permits me I would be fixing as many as I can...
FYI - VOTING is not only for a particular version or is not only managed by release manager for a specific version. if I'm not mistaken. And only committee members can make decision on changing that - that's Dims I know, Sanjaya will manage 1.5 and will do a great job on that. And hope you are not managing and making decisions - but the team does. Finally lets stop 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 there is a right time for everything. While there are *more important things* like fixing Jira issues are pending it is a *waste of time* at this point in time to go on discussing this. I would have more interested in, if you were to discuss how many Jira isses you could be fixing for 1.5 and would make lost of sense at this point in time. If you are really serious about the betterment of the project that is the best available option at this point in time is to have a look at Jira and do some code fixes. There is a release manager already for 1.5, and I think he will take care of the release plan as proposed already. And the release manager will take care of those *VOTES* as well. Samisa... On Fri, 21 Jan 2005 02:33:29 -0500, Lilantha Darshana <[EMAIL PROTECTED]> wrote: > Starting a thread of discussion for future releases does not need to be > in a specific time interval. And is quite clear, that this effort is not for > changing the already set plans for 1.5. However, for upcoming version > which we have not set dead line for, we need agreeing on this after a > 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 > <[EMAIL PROTECTED]> wrote: > > Every body 100% agree on that and have no question about fixing defect and > > providing them as soon as ppl expect them in what ever versions we release > > next. I know you guys have spent quite a lot of your valuable time on that. > > > > Here the effort is to little bit change the model on what we used to do > > since 1.1 until now. and focusing on to reduce number of defects > > we *introduce* each time by having better understanding and a collaboration > > model. That's why we need discussing even about proper version > > numbering scheme, IMO. Some time, these kind of discussion goes too far > > when ppl have +ve/-ve arguments. anyway, that's need to be there. > > > > Now if you carefully analyze the past, we can figure out, why we have > > 100+ defects for 1.5? Do we need to go on like that until we satisfy only > > few > > users OR we do a careful analyze and make things better and provide > > what users expect, and by adhering to the technology trend - and finally > > with less defects. That's save every bodies valuable time I hope. > > There could be this many issues due to couple of reasons: > 1. Developers have done too bad job and has done only feature addition > without doing a quality job > 2. There are many people testing the product as a result of widespread > use and because there is a formal test strategy in place > > I go with the second reason and would like to provide fixes to as many > as possible. Because people are using it and they report problems with > the hope the issues would be fixed. > > I am sorry that you have started this thread on the eve of 1.5 > release. Many have their plans laid around this release. This > discussion would have been done way back in October 2004 when 1.3 was > done. Because there were so many lengthy discussions on 1.4 and 1.5 at > that time, and there was some agreemt over the timelines and set of > features and version numbers. > > It is not the right time to continue on this. May be after 1.5, before > 1.6. But not 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 still believe fixing stuff is more important at the moment than > > bothering about numbering. > > > > In the recent past, fixing issues was the main focus, and dilivering > > the fixes to users ASAP in the form of releases. > > There has been and there is enough discussion going on reagrding plans > > to fix pending issues, from 1.1 through to 1.5 - we did not release > > all these without reason - but with enough fixes and features. > > > > Samisa... > > > > On Thu, 20 Jan 2005 23:42:05 -0500, Lilantha Darshana > > <[EMAIL PROTECTED]> wrote: > > > mmm... Right, that's why we need a collaborative discussion about > > > visioning here and have a better plan for future. And that makes > > > every one aware of what need doing to make this success. > > > > > > thanks > > > -Lilantha > > > > > > > > > -----Original Message----- > > > From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] > > > 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 fixing them, given that current active > > > developrs are fixing as much as they can and are fully occupied doing > > > the same. > > > > > > Samisa... > > > > > >
