diff options
author | David Golden <dagolden@cpan.org> | 2013-06-20 16:20:29 -0400 |
---|---|---|
committer | David Golden <dagolden@cpan.org> | 2013-06-20 16:20:29 -0400 |
commit | 2136887ad30a1425b280c82b31b2990f42b1ed91 (patch) | |
tree | aaf79020018e41d13722c2af887810ee22c6185b | |
parent | 5c53df946578f1592c535239f881bb64c953e7be (diff) | |
download | perl-2136887ad30a1425b280c82b31b2990f42b1ed91.tar.gz |
Fix Perl version references in INSTALL
Also update the RMG to remind people to do this for the "late" bumps in
BLEAD-POINT and BLEAD-FINAL releases
-rw-r--r-- | INSTALL | 4 | ||||
-rw-r--r-- | Porting/release_managers_guide.pod | 2 |
2 files changed, 4 insertions, 2 deletions
@@ -2431,9 +2431,9 @@ seriously consider using a separate directory, since development subversions may not have all the compatibility wrinkles ironed out yet. -=head2 Upgrading from 5.17.11 or earlier +=head2 Upgrading from 5.19.0 or earlier -B<Perl 5.19.1 may not be binary compatible with Perl 5.17.11 or +B<Perl 5.19.1 may not be binary compatible with Perl 5.19.0 or earlier Perl releases.> Perl modules having binary parts (meaning that a C compiler is used) will have to be recompiled to be used with 5.19.1. If you find you do need to rebuild an extension with diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index e6848601db..0995866472 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -1157,6 +1157,8 @@ in the remaining files and test and commit. If this was a BLEAD-POINT release, then just follow the section L<"Bump the version number">. +After bumping the version, follow the section L<"update INSTALL"> to +ensure all version number references are correct. =head3 clean build and test |