diff options
| author | Jesse Vincent <jesse@bestpractical.com> | 2011-06-30 20:40:54 -0400 |
|---|---|---|
| committer | Jesse Vincent <jesse@bestpractical.com> | 2011-06-30 20:40:54 -0400 |
| commit | 4899916ae02f106df163459798ebe3b2a863afb6 (patch) | |
| tree | fd9fe9eaf08ea0496494bb49b3399a360a851c20 | |
| parent | f1905e1b1b0d9cd2c673369524247d7a0280d166 (diff) | |
| download | perl-4899916ae02f106df163459798ebe3b2a863afb6.tar.gz | |
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
| -rw-r--r-- | Changes | 4 | ||||
| -rw-r--r-- | Porting/release_managers_guide.pod | 16 |
2 files changed, 2 insertions, 18 deletions
@@ -12,9 +12,9 @@ at http://perl5.git.perl.org/perl.git (follow the 'shortlog' link beside the relevant tag). Or, you can download a copy of the git repository and then run a command like - git log --name-status v5.14.0..v5.15.0 + git log --name-status v5.12.0..v5.14.0 -to view all the changes between 5.14.0 and 5.15.0. +to view all the changes between 5.12.0 and 5.14.0. See pod/perlgit.pod for more details on using git and accessing the commit history. 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<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). - - =head3 Check more build configurations Check some more build configurations. The check that setuid builds and |