Okay, because we've been moving things around, renaming classes etc
we've reached the point where the current API is more than a little
different from the 'old' API. Which generally means you need to
increment the major version number.
And, dammit, the framework is really useful now and creeping towards
maturity. I'm thinking of picking the current trunk (with a working
'ok') and tagging it 1_0_RELEASE_CANDIDATE freezing the features,
hammering on it to make it work with 5.7.2, writing a quick tutorial
pointing people at Test::Unit::TestCase and getting it up to CPAN as
1.0 as soon as we're happy with it. The Roadmap for this, as I see it
is:
1. Rename Test::Unit to Test::Unit::Procedural
2. Rename Test::Unit::HarnessUnit and Test::Unit::UnitHarness
Not sure what to yet, but I want to get these big API changes out
of the way before we bump the version number.
3. Working ok
4. Working build on 5.7.2
Nice to have
1. Test::Unit::Loader working with whole directories.
2. <YOUR SUGGESTIONS HERE>
--
Piers
"It is a truth universally acknowledged that a language in
possession of a rich syntax must be in need of a rewrite."
-- Jane Austen?
_______________________________________________
Perlunit-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/perlunit-devel
