Are we near to seeing stuff commited.. ? apart from the obvious fact that some contentious items can be vetoed *after* commit, I'd say that as long as it builds we should be commiting often.
d. > -----Original Message----- > From: Peter M. Goldstein [mailto:peter_m_goldstein@;yahoo.com] > Sent: 25 October 2002 18:23 > To: 'James Developers List' > Subject: RE: Code change the Apache way > > > > Serge, > > > > - 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?" > > Agreed. One minor correction. Performance improvement isn't 30%, it's > 900%. Prior to these changes James crashed under a load of ~6 > mails/second (360 mails/minute). With the current code base (Watchdog, > object pooling, deleteonexit removed) we are getting a performance of > ~60 mails/second (3600 mails/minute). > > --Peter > > > > -- > 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>
