summaryrefslogtreecommitdiff
path: root/Porting/release_managers_guide.pod
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2011-07-16 19:14:23 -0700
committerFather Chrysostomos <sprout@cpan.org>2011-07-16 19:14:23 -0700
commit9709cbd8336f0eb5064c0b8ffd39c7ad416656c6 (patch)
tree53dfc5113da5b1d713e053a2945f415886ef2eb1 /Porting/release_managers_guide.pod
parentaebc0cbee0c83e7c1648507658f739153cf1176a (diff)
downloadperl-9709cbd8336f0eb5064c0b8ffd39c7ad416656c6.tar.gz
porting/rmg: Expand on CoreList version bump
Diffstat (limited to 'Porting/release_managers_guide.pod')
-rw-r--r--Porting/release_managers_guide.pod3
1 files changed, 3 insertions, 0 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 1525d32df0..c58bc205ed 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -447,6 +447,9 @@ Check that file over carefully:
If necessary, bump C<$VERSION> (there's no need to do this for
every RC; in RC1, bump the version to a new clean number that will
appear in the final release, and leave as-is for the later RCs and final).
+It may also happen that C<Module::CoreList> has been modified in blead, and
+hence has a new version number already. (But make sure it is not the same
+number as a CPAN release.)
Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >>
entry, as that is likely to reflect the previous version number.