mirror/perl
1
0
Fork 0
mirror of https://github.com/Perl/perl5.git synced 2026-01-27 01:44:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change the example in the Changes file to be more generic.

Browse Source 
Remove the releng step which required altering the Changes file
with a meaningless version bump
This commit is contained in:
Jesse Vincent 2011-06-30 20:40:54 -04:00
parent f1905e1b1b
commit 4899916ae0
2 changed files with 2 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Changes
View File

@ -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.

16
Porting/release_managers_guide.pod
View File

@ -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