Metabase profile generation will use as much of the provided email_from parameter as possible and will generate a random secret API key. If user provides email_from in a standard form like C<< "John Q. Public" <jqp@example.com> >> then profile generation is entirely automatic without additional prompts from metabase-profile [David Golden]
DOCUMENTATION
Swapped in Task::CPAN::Reporter in the SYNOPSIS [David Golden]
BUG FIXES
Expands "~" into user directory before attempting to locate 'relative' pathname in .cpanreporter directory [David Golden]
Changes for version 1.19_03 - 2011-06-28
NEW FEATURES
During configuration, if 'Metabase' is the requested transport and a Metabase profile file is not found, configuration will offer to run metabase-profile to create it. [David Golden]
For Metabase transport (only), the 'id_file' may have a relative file path, treated as relative to the .cpanreporter directory.
David Golden
BUG FIXES
updated CPAN::Reporter to go with Metabase by default, instead of the deprecated SMTP transport system. This provides more up-to-date information for new testers on how to setup their systems and addresses RT#64316 (and maybe also RT#61735) [Breno G. de Oliveira]
Replaced use of Tee.pm with Capture::Tiny as the two don't play well together on some systems. [Christian Walde]
DOCUMENTATION
Docs have been substantially re-written to reflect the new HTTP-based transport instead of email-based transport. [Breno G. de Oliveira and David Golden]