On 1/20/07, Ovid <[EMAIL PROTECTED]> wrote:
Obviously, nothing will get renamed to Test::Harness without Andy Lester's blessing. Further, nothing will simply be 'rushed into place' without extensive testing and we want to feel *extremely* comfortable that we're not going to break anything. We want this to be *completely* backwards compatible, but would like to hear feedback from folks about any issues we might want to be aware of.
Speaking for CPAN::Reporter, since it relies on parsing the output from Test::Harness to interpret success or failure, there's certain to be some work to ensure forward compatibility. I believe all the CPANPLUS-derived smokers may likewise need CPANPLUS tweaks for any changes to Test::Harness output, but I don't know enough to be sure. I'll admit I haven't looked closely at TAPx::Parser -- if there's a more structured way to get test results back than parsing, that would be ideal. Either way, there will need to be logic for $Test::Harness::VERSION >= 3. I guess it's time for me to start experimenting with TAPx::Parser... David
