TH3 Sooner Rather Than Later

[Ovid]

Hi all,

I think we're getting distracted by side issues.  We have ONE goal:

Getting TH3 out the door.  Personally, I think that parallelization is
an appropriate target for 3.1, others seem to feel that 3.0 is OK, but
if parallelization is going to hold things up, I'd be for a TH3 release
with the parallel work following shortly thereafter.  There are a
couple of reasons for this:

1.  We need to get TH3 out the door.  People are asking me about it and
they want it.  Parallel tests are wonderful gravy, but still gravy.

2.  We're going to get bug reports for 3.0.  They could be nasty.  I'd
rather not get them for our basics *and* for the parallel work. 
There's no need to bite off more than we can chew.

We seem to be getting distracted on side issues.  Right now, what about
releasing it and making it clear that the plugin/inheritance/whatever
architecture functionality may change?  The Test::Harness interface is
stable and the prove interface is stable.  This satisfies 99% of our
base.

I do realize that by putting out TH3 a bit early, we could wind up with
the problem of having to change things later, but I think the wider
exposure could expose us to the *real* problems we face rather than the
problems we're trying to solve in a vacuum.

By this strategy, we can mark *parallel* as experimental (or completely
pull it back to a branch), test on VMS and push this out.  The *only*
major caveat is that we don't break the toolchain.  We're not likely to
do that, right?  So let's consider pulling the trigger and stop getting
distracted :)

Cheers,
Ovid

--
Buy the book  - http://www.oreilly.com/catalog/perlhks/
Perl and CGI  - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog     - http://use.perl.org/~Ovid/journal/