Given the discussion on various threads ("community package maintenance"
etc.), we've decided to incorporate the tests back into the image, so
that they're close to the code.  So this is approved.

As long as the tests follow the naming conventions (which these do) of
being in their own class category prefixed with 'Tests-', and have tests
on specific classes postfixed with 'Test' (e.g. WriteStreamTest), the
tests should be easy to separate out into packages when the
corresponding tested code is moved into packages.

- Doug














<This post brought to you by BFAV2>