Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

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
  • Loading branch information...
1 parent f1905e1 commit 4899916ae02f106df163459798ebe3b2a863afb6 @obra obra committed
Showing with 2 additions and 18 deletions.
  1. +2 −2 Changes
  2. +0 −16 Porting/release_managers_guide.pod
4 Changes
@@ -12,9 +12,9 @@ at (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.
16 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

0 comments on commit 4899916

Please sign in to comment.
Something went wrong with that request. Please try again.