From 4899916ae02f106df163459798ebe3b2a863afb6 Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Thu, 30 Jun 2011 20:40:54 -0400 Subject: Change the example in the Changes file to be more generic. Remove the releng step which required altering the Changes file with a meaningless version bump --- Porting/release_managers_guide.pod | 16 ---------------- 1 file changed, 16 deletions(-) (limited to 'Porting/release_managers_guide.pod') diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index f097846fee..a18c4a5903 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -339,22 +339,6 @@ release, this would be 5.13.11). For BLEAD-POINT releases, it needs to refer to the previous BLEAD-POINT release (so for 5.15.3 this would be 5.15.2). - -=head3 update Changes - -Update the F 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 and see -if C produces roughly the right number of commits across roughly the -right time period (you may find C useful). - - =head3 Check more build configurations Check some more build configurations. The check that setuid builds and -- cgit v1.2.1