On Sun, Feb 19, 2006 at 08:30:12PM +1100, Adam Kennedy wrote: > Yitzchak Scott-Thoennes wrote: > >>And if we can clear Module::Build on 400-500 installations of Perl, I'd > >>feel much more comfortable about seeing it head towards the core. > > > >Sigh. It's a perl-only module; putting it in is not going to break > >any builds, at worst it will fail its tests. And if it is going to > >fail tests on platform Foo, we want to know that as soon as possible, so > >that's a good thing. > > > >I greatly appreciate it that you want to test it on so many perls, but > >that's not a substitute for the variety of platforms doing smoke tests > >or other periodic testing of the core. > > > >It scares me that modules like "version" are switching to Module::Build > >and we don't have any sense for how many platforms it just plain doesn't > >work on. The sooner it's in the core, the better. > > When I say "perls" I include platforms. > > 15-odd production releases from 5.004 up, and 10-20 common platforms + > variations.
What platforms? > And we're much more likely to get uniform coverage by testing all of > them in advance in an automated fashion than just sending it off to core > and waiting for bug reports from individuals. Right. Testing in the core isn't a substitute for what you are proposing either. So do both.
