Schwern

To keep myself focused on getting a feature complete Test::Builder 1.5 out this month, I've been writing down non-critical tasks rather than doing them myself. Refactorings, documentation and interface fixups. They're helpfully categorized:

• Easy are things which are easy.
• Gardening are refactorings and other cleanups.
• Docs are for documentation.

If you'd like to help, I'd love the help. There's plenty to do for everybody. Our preferred workflow is laid out and pretty easy to follow. There's a design document to give you an overview of what's going on, though it is out of date in places.

When the Google Code In starts, these tasks will be made available for GCI students.

About Test::Builder2

As you may or may not know, a major rewrite of Test::Builder (the thing which coordinates and does the heavy lifting for the Test modules) has been in the works for some time. Called Test::Builder2, it has a grant from The Perl Foundation. The grant's final deadline is at the end of the month and I'm frantically coding to get a feature complete alpha out in time.

This release is being referred to as Test::Builder 1.5. It contains all the internal reworkings of Test::Builder2, but in order to save time the new class to replace Test::Builder itself (which is also called Test::Builder2) is not done.

But users still get to use and benefit from the new internals!