Add any targets that you're aiming for during the hackathon.

Don't forget to put your name next to your entry.

Module::Build replacement

Write various components of a planned Module::Build replacement, including

• Finish the prototype, Module::Build::Tiny.
• Finish ExtUtils::Builder, a general purpose compiling/linking framework
• Write a dependency engine that doesn't suck
• Tie everything together and write the actual thing itself

By: Leon Timmermans (‎leont‎)

Installed module database / Packlists replacement

Write a .packlist replacement, see this thread

By: user:Schwern, Leon Timmermans (‎leont‎), others?

Finish the Build.PL specification

The Build.PL specification needs to be finished
By: xdg?, Leon Timmermans (‎leont‎)

CPANTS Kwalitee metrics

Implement some of the proposed kwalitee metrics

By: Kenichi Ishigaki (‎charsbar‎), Olivier Mengué (‎dolmen‎) (H.Merijn Brand (‎Tux‎) is interested in giving feedback and user input)

Test::Smoke and Test::Smoke::Gateway

Now that the gateway works and is on-line and receiving since the last QAH, we
need to polish the UI and define some selection criteria that will help the p5
developers get in-depth analysis out of the stored data.

By: H.Merijn Brand (‎Tux‎), Abe Timmerman (‎abeltje‎)

Test::Database

The module reached version 1.00 thanks to the QA Hackathon in Birmingham.

I recently found out that it's actually used by some projects, so it's certainly worth spending some time on improving it.

By: Philippe Bruhat (‎BooK‎)

CPAN.pm enhancements

• Finish internal logic refactoring work from Paris (xdg)
• Streamline CPAN mirror selection to use www.cpan.org, now that it's a GTLD balanced server supported by Perl NOC (xdg)
• Continue new index implementation work from Paris (xdg)

By: David Golden (‎xdg‎)

CPAN Testers

• Pending availability of donated servers, migrate Metabase off AWS (xdg)

By: David Golden (‎xdg‎)

Show some sweet, sweet love to Test::Harness

I have three main targets for this hackathon, all surrounding Test::Harness. I would like feedback from people regarding which of the three targets is the most valuable so that I can better prioritize my time.

1. I intend to work on the bug queue for . Fortunately, many issues are merely annoyances and not actual bugs.

2. Parsing subtests. Tools built around the underlying TAP::Parser pretty much have to ignore subtests (except for the summary line). This should be fixed. Andy Armstrong assured me that this wasn't just a few minutes worth of work and I thought "naw, this should be quick." I was wrong. This is a non-trivial problem requiring two phases. The first is to parse the subtests. The second is to extend the event system to trigger on subtests, lest our code block until each subtest is finished.

3. Add --startup, --setup, --teardown, --shutdown switches to prove:

prove -lr --startup tools/create_db \
--setup   tools/refresh_tables      \
--shutdown tools/destroy_db         \
t/

By: user:ovid

Get Test::* all passing with Test::Builder 1.5

This is a focused effort to get all of the Test::* modules on CPAN working with Test::Builder 1.5.

The largest obstacle to releasing Test::Builder 1.5 is roughly 100 of 1000 Test::* modules fail when using it. Some are functional differences, but mostly these are small differences in test output formatting.

This will be accomplished by several means, many of which can be done by anyone familiar with writing tests.

* Fixing revealed problems in Test::Builder 1.5.
* Writing/improving a Test testing module which works across the 0.9x / 1.5 line.
* Patching the failing Test::* modules' test suite to work with 1.5.
* Possibly rolling back formatting changes in Test::Builder 1.5.

By: user:Schwern

version 15 saved on 04/02/13 01:23 by Michael Schwern (‎Schwern‎)

Home | Tags | Recent changes | History