summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2010-01-20 20:23:16 -0500
committerRicardo Signes <rjbs@cpan.org>2010-01-20 20:23:16 -0500
commit6642915e130e2410e5cc7d1e00a39aa7b8774d05 (patch)
treebfa8e8665d65a42bd50a0572cf0f8b9429db8d05 /Porting
parent603fcd17d4a074139fc76d9d159b3d2d71869bb2 (diff)
downloadperl-6642915e130e2410e5cc7d1e00a39aa7b8774d05.tar.gz
remove defunct "Changes" file step from RMG
Diffstat (limited to 'Porting')
-rw-r--r--Porting/release_managers_guide.pod17
1 files changed, 0 insertions, 17 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 8bdb58ff33..f3a139a9b7 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -151,7 +151,6 @@ in having one for a snapshot, but it's not required).
=back
-
=head2 Building a release - advance actions
The work of building a release candidate for a numbered release of
@@ -328,22 +327,6 @@ in particular, the "Coexistence with earlier versions of perl 5" section.
=item *
-I<You MUST SKIP this step for SNAPSHOT>
-
-Update the F<Changes> file to contain the git log command which would show
-all the changes in this release. You will need assume the existence of a
-not-yet created tag for the forthcoming release; e.g.
-
- git log ... perl-5.10.0..perl-5.12.0
-
-Due to warts in the perforce-to-git migration, some branches require extra
-exclusions to avoid other branches being pulled in. Make sure you have the
-correct incantation: replace the not-yet-created tag with C<HEAD> and see
-if C<git log> produces roughly the right number of commits across roughly the
-right time period (you may find C<git log --pretty=oneline | wc> useful).
-
-=item *
-
Check some more build configurations. The check that setuid builds and
installs is for < 5.11.0 only.