Hi Harmeet, > - Keep scope as close to what is being attempted. We have been making more > design changes than a bug fix/cleanup needs.
Yes which are fixing show-stopper bugs and improving performace by 30% +. Whats an email server if you can't count on it to do its job? How many people keep asking "is it production ready?" Thanks, Serge ----- Original Message ----- From: "Harmeet Bedi" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Friday, October 25, 2002 6:56 PM Subject: Re: Code change the Apache way > We seem to have extremely strong views over things that are of marginal > importance. My rule of the thumb is usu. to not do minor cleanup(like > removing one not useful for now class) if someone objects. This also sits > well with rules but there is no point arguing endlessly about it. Willing to > give in... :-( > and eager to move to other things. :-) > > > Some suggestions to facilitate changes: > - Cleanup/redesign few things at a time not 5 things together > - Keep scope as close to what is being attempted. We have been making more > design changes than a bug fix/cleanup needs. > > This was a really nice thing to say : > From: "Serge Knystautas" <[EMAIL PROTECTED]> > > saying the rules and regs aren't heavy and not a big part of > > the culture > > Harmeet > > > -- > To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
