2 guidelines to avoid regressions. I believe proposals guideline is part of Jakarta, and James has used it effectively.
1. Have risky or major refactoring in the proposals area and move them to head after there has been some testing and review. 2. Run a minimal end user test(say something that can be done in 5 mins) after refactoring. Of course if it is automated all the better. Could this be incorporated into a set of project guidelines for James. I believe it would make everybody more productive. As James grows in size/ambition some simple guidelines could yield a lot of benefit. James/Apache developers are a talented group but it is possible to miss things as each person usu. has more than enough things on the plate. A check list and self discipline may help even the best. thanks, Harmeet
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
