On Saturday 02 May 2015 15:36:48 David Golden wrote: > There are only a handful of really commonly used Test::* libraries and I > suspect that they could be forked to use Test::Builder2 trivially, as few > of them wind up needing the interesting new bits. Only the Test::* modules > that were monkey patching or can take advantage of hooks would need any > real revision.
So as the author of Test::WWW::WebKit, I'd have to offer two different variants of my module, even though the only difference would probably be the "use Test::More" line? And if we wanted to use the new Test::More2 possibilities, we'd probably have to have a flag day change from Test::WWW::WebKit::Catalyst to the Test::More2 version, and at the same time change to a Test::WWW::Mechanize::Catalyst version supporting Test::More2. Or as alternative, we'd have to do without the new features and stay with the old Test::More and a probably uncertain future? Because maintaining and old version where you cannot make incompatible changes is even more boring when the new framework that fixes many long standing issues is already there. To me this future sound like an even larger burden for downstream. Stefan
