Gentlemen, a call to arms!
Matt S Trout
dbix-class at trout.me.uk
Thu Oct 12 20:18:20 BST 2006
> On Thursday 12 October 2006 04:18, Paul Makepeace wrote:
>> I wonder if there's some scope for a module author to have other
>> highly dependent modules/applications register themselves as
>> interested parties who/that would appreciate builds of their
>> modules/applications to be tested before said module is released. You
>> could even do this automatically by keeping stats on CPAN downloads
>> and looking at the dependency graph. "Ah, there's this enormous app
>> that requires my module, perhaps I should try building $enormous_app
>> before I ship my latest & greatest."
> Bleh. I'm happy to *notify* developers who use my code (especially if it's
> easy), but I don't want to get in to waiting for everyone to upgrade and test
> before I can release something.
I'd be over the moon with "notify with dev release and a deadline to test by",
assuming the deadline is at least a few days - I think a week would probably
be an ideal compromise between making sure people have testing time and not
holding a release up from my POV.
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
More information about the london.pm