Re: On Not Merging new and old behavior ( was Re: Test-Stream + MongoDB scalar refcount issue )

On Sat, May 2, 2015 at 3:49 PM, Stefan Seifert <[email protected]> wrote:

> 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?
>
>
Yes.  Though you could, if you wish, declare Test::WWW::Webkit to be
end-of-life.  (Unless another maintainer takes over.)


> 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.
>
>
It depends how tightly coupled all those modules are -- whether they use
Test::Builder directly or not.  In the case of Test::WWW::WebKit::Catalyst,
I didn't see anything in the code that would require any changes.


> 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.
>

Exactly.  People who want old and stable can choose it.  People who want
new and hopefully-stable can choose it.

David



-- 
David Golden <[email protected]> Twitter/IRC: @xdg