diff options
author | Steve Hay <steve.m.hay@googlemail.com> | 2020-10-16 08:19:03 +0100 |
---|---|---|
committer | Steve Hay <steve.m.hay@googlemail.com> | 2020-12-18 12:24:39 +0000 |
commit | ab31a05b2fcb3a1e1f1844d64994b84514db22d4 (patch) | |
tree | 8f7209bfdbb769910f1289a7f6eb1675fa4fdc5f /Porting | |
parent | a18d0e462e083878bba05847e1159fb15b373f6a (diff) | |
download | perl-ab31a05b2fcb3a1e1f1844d64994b84514db22d4.tar.gz |
RMG - Spelling and grammar tweaks
(cherry picked from commit 2c81b40555d63d164de3b0b4054b12ec9e02cd86)
Diffstat (limited to 'Porting')
-rw-r--r-- | Porting/release_managers_guide.pod | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index a4b610514f..ecc6055a99 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -510,8 +510,8 @@ blead release, so you may find nothing to do here. =head3 update AUTHORS -AUTHORS file can be updated by running C<Porting/checkAUTHORS.pl --update> -The script detects missing authors or commiters since the last release using +The AUTHORS file can be updated by running C<Porting/checkAUTHORS.pl --update> +The script detects missing authors or committers since the last release using a known tag provided by the C<--from=v5.X.Y> argument, and will add missing entries to the AUTHORS file. @@ -521,17 +521,17 @@ For MAINT and BLEAD-FINAL releases, C<v5.X.Y> needs to refer to the last release in the previous development cycle (so for example, for a 5.14.x release, this would be 5.13.11). -BLEAD-POINT releases, it needs to refer to the previous BLEAD-POINT +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). -Note: this should not be harmful to use a wider range. +Note: It should not be harmful to use a wider range. -Note: if you have uncommited changes this could cause some warnings, -and you would like to use the addtional argument C<--to=upstream/blead> +Note: If you have uncommitted changes this could cause some warnings, +and you might like to use the addtional argument C<--to=upstream/blead> to use the last known git commit by GitHub. -Review the changes to the AUTHORS file, be sure you are not adding duplicates -entries or removing some AUTHORS, then commit your changes. +Review the changes to the AUTHORS file, be sure you are not adding duplicate +entries or removing any entries, then commit your changes. $ git commit -a AUTHORS -m 'Update AUTHORS list for 5.x.y' |