For the purposes of better (more robust) collaboration
with bug fixes for PDL development, I suggest we
implement the following bug report/repair strategy which
I've been trying with my own fix submissions:
1. Add a test to t/ as either a new file or an additional test
in an existing test file which generates a fail for the bug.
2. Fix the bug and verify that the test now passes
3. Commit changes to CVS with documentation.
This will help us better track which platforms have which
bugs. It will add regression testing for each bug fixed to
all release platforms. And, it will help us sort out issues
where a fix works for one platform but breaks on another.
--Chris
Apologies for the pdl-porters and perldl list cross posting
but I wanted to be sure to get potential 2.4.4 developers.
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
