I would actually suggest that if someone adds code and it exposes a bad
test then they should be required to fix the testcase as well _before_ they
commit the entire lot. "ant clean all-tests" should _always_ work.
-Dug
James M Snell/Fresno/[EMAIL PROTECTED] on 02/28/2003 01:03:51 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: Check-in's till 1.1 Final Release...
-1 to all automatic roll backs based on a run clean all-tests failure. In
order to respect the work other people are doing to actually shrink the
buglist, folks should take the time to first see if it's a problem in the
test case that's causing the failure rather than a problem with the fixed
code. If a test fails, please take the time to figure out why.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(559) 587-1233 (office)
(700) 544-9035 (t/l)
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
Davanum Srinivas <[EMAIL PROTECTED]>
02/28/2003 09:43 AM
Please respond to axis-dev
To
[EMAIL PROTECTED]
cc
bcc
Subject
Check-in's till 1.1 Final Release...
Folks,
PLEASE RUN "ant clean all-tests" before checking things in. If anything
breaks Gump build ("ant
clean all-tests") that qualifies for an automatic -1 from me. Also, BEFORE
you run "ant clean
all-tests", GET the latest sources from CVS...ALSO, PLEASE don't introduce
JDK1.4 specific code.
It's TOO late in the game to check-in code and expect others to fix
problems that were introduced.
Thanks,
dims
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
