Given that you are going to commit this code, I don't see any benefit in posting new updates without committing. Surely we want to be testing this as much as possible and this is much easier to do out of CVS rather than CVS plus patches.
Regards Steve > -----Original Message----- > From: Peter M. Goldstein [mailto:peter_m_goldstein@;yahoo.com] > Sent: Friday, October 25, 2002 10:58 AM > To: 'James Developers List' > Subject: RE: Code change the Apache way > > > > Danny, > > > 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. > > Noel and I are currently running more tests, and everything > is coming up green. What I will do is post the latest, > greatest code for evaluation later today. If the consensus > is that I should commit said code, I'll be more than happy to > do so. I have simply been unwilling to do so over an outstanding -1. > > --Peter > > > > -- > To unsubscribe, e-mail: > <mailto:james-dev-> [EMAIL PROTECTED]> > 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>
