summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorÆvar Arnfjörð Bjarmason <avar@cpan.org>2011-02-20 15:41:15 +0000
committerÆvar Arnfjörð Bjarmason <avar@cpan.org>2011-02-20 15:42:04 +0000
commitcb9af4c0df448d46ed5d17cc25f1ba1373d74982 (patch)
treea14f3589399bba66e90954c87551a21ef1fe7371 /Porting
parent28fcd4224f1953859628f8dfd1b0cd6a8ee5d4a0 (diff)
downloadperl-cb9af4c0df448d46ed5d17cc25f1ba1373d74982.tar.gz
Porting/release_managers_guide.pod: Module::CoreList has no META.yml file
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.
Diffstat (limited to 'Porting')
-rw-r--r--Porting/release_managers_guide.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 3e1172ee32..1f82a692db 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -489,8 +489,8 @@ appear in the final release, and leave as-is for the later RCs and final).
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