Re^2: Is maintaining multiple versions of a CPAN module a terrible idea?


The stupid question is the question not asked
	PerlMonks

Re^2: Is maintaining multiple versions of a CPAN module a terrible idea?

by Arunbear (Prior)

on Jun 06, 2014 at 10:26 UTC ( [id://1089009]=note: print w/replies, xml )

Need Help??

in reply to Re: Is maintaining multiple versions of a CPAN module a terrible idea?
in thread Is maintaining multiple versions of a CPAN module a terrible idea?

What's the ETA of Type::Tiny 1.000000 ?

Comment on Re^2: Is maintaining multiple versions of a CPAN module a terrible idea?

Replies are listed 'Best First'.

Re^3: Is maintaining multiple versions of a CPAN module a terrible idea?
by tobyink (Canon) on Jun 09, 2014 at 08:34 UTC

Good question. "When it's ready." Hopefully this year.

I don't envisage any major API changes before 1.000000. I mostly just want to improve the test suite coverage. I haven't had as much time to work on that as I might have liked, but generally speaking I've found that time spent doing this has been worthwhile in terms of finding obscure (but potentially important) bugs.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

[reply]

In Section Seekers of Perl Wisdom