On Tue, Feb 21, 2017 at 10:15:03AM +0000, Dave Mitchell wrote: > The regen.t one I just fixed with v5.25.10-21-g3ae5079, but > the CoreList ones I don't understand and am hoping someone with better > knowledge will handle that instead. I've now fixed with too with v5.25.10-22-gb25fc2a. It appears that some steps in the RMG were skipped, specifically: =head4 Bump Module::CoreList* $VERSIONs =head4 Update C<Module::CoreList> with module version data for the new release. $ ./perl -Ilib Porting/corelist.pl cpan =head4 Bump version in Module::CoreList F<Changes> But I found it very confusing, as the version number for Module::CoreList appears to need to be bumped one month in advance - i.e. on 20th January Abigail bumped it to 5.20170220, and I've just bumped it further to 5.20170230. If those are correct, then perhaps this convention needs explaining in the RMG? -- A walk of a thousand miles begins with a single step... then continues for another 1,999,999 or so.Thread Previous | Thread Next