During my in-progress release:
$ git --no-pager grep 2.44 -- ./dist/Module-CoreList/
dist/Module-CoreList/Changes:2.44 Sat Jan 22 2011
dist/Module-CoreList/lib/Module/CoreList.pm:$VERSION = '2.44_01';
dist/Module-CoreList/lib/Module/CoreList.pm: 'Module::CoreList' => '2.44_01',
It doesn't have a META.yml anymore, instead a MYMETA.yml is generated
for us. So the bit that told us to update it in
Porting/release_managers_guide.pod was out of date.
Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >>
entry, as that is likely to reflect the previous version number.
-Also edit Module::CoreList's new version number in its F<Changes> file and
-in its F<META.yml> file.
+Also edit Module::CoreList's new version number in its F<Changes>
+file.
You should also add the version you're about to release to the
L<Module::CoreList/CAVEATS> section which enumerates the perl releases