Hiya,
I have for long wanted to get my hands dirty with M::B, I have made
several subclasses, but I would like to get more into depth with M::B.
So if there is anything I could do, I would gladly help and hopefully
I could help to free up some resources to look at something like the
plugin system.
So if you have some designated tasks I would love to look into
creating some patches or tests.
jonasbn
On 12/09/2008, at 09.10, Eric Wilhelm wrote:
Hi all,
I've backed-out r10222 and r10224 and shipped 0.2808_04.
Unless somebody points out that this has the exploding chipmunk nature
in the next couple of days, I think it is safe to say we can ship 0.29
before Monday. (I'm tempted to bump the version number to 0.3 just to
save the typing at this point.)
Moving on from that, my current wishlist:
* new 'N' key for my laptop :-(
* test coverage for this module_name + dist_version_from case
(my broken feature had test coverage, which has also been reverted)
(bah)
* testcover working (more on that later)
* M::B should pass its own testpod
* M::B should pass its own testpodcoverage[1]
* test coverage for any uncovered, documented feature
* oh crap, the RT queue?!
* any sort of automated smoke system that isn't cpantesters[2]
Given one or more of these, I'll ship 0.4 within a month.
[1] Its own testpodcoverage need not be Test::Pod::Coverage, but
whatever it is - it should (A) do some kind of verification that the
pod that should be written is written and (B) pass!
[2] It could be cpantesters, but I would rather see M::B tests against
the CPAN running (A) out-of-band to minimize "author WTF" and (B) from
svn. The current state of things is that we have very low test
coverage, which means that the CPAN needs to be out test suite, but
the
way this currently runs through cpantesters requires me to (B) release
a tarball and will (A) spam everybody but me about it.
So, that's the current state of things. I think I can tolerate
pushing
the tarballs and applying patches right now, but I haven't got time
for
much else and that still doesn't leave time for me to take a crack
at a
plugin system or much of anything else that I would actually enjoy
hacking on. With 2000+ distributions, not much test coverage, and no
smoke process, I basically don't feel like I can actually *do*
anything.
Do we need to hand out more commit bits or candy or what?
Thanks,
Eric
--
"It works better if you plug it in!"
--Sattinger's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
