summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Koenig <root@dubravka.in-berlin.de>2022-11-15 05:57:13 +0100
committerJames E Keenan <jkeenan@cpan.org>2022-11-18 17:52:29 -0500
commita33534361e54c6342c59edd0c06b6bbb9ac5776c (patch)
tree726d91d7e0ed302ffeff0e5f8ea38951165c31d2
parent0507844a31371da4dbf9136341e30487e5a9b5a8 (diff)
downloadperl-a33534361e54c6342c59edd0c06b6bbb9ac5776c.tar.gz
clarify that every tag is required to be annotated
- while the instructions were already clear at this point, accidents with lightweight (unannotated) tags have happened
-rw-r--r--Porting/release_managers_guide.pod12
1 files changed, 11 insertions, 1 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index dfb6505afd..8885f7f9bb 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -938,7 +938,7 @@ Then delete the temporary installation.
=head3 create the release tag
-Create the tag identifying this release (e.g.):
+Create the I<annotated> tag identifying this release (e.g.):
$ git tag v5.11.0 -m 'First release of the v5.11 series!'
@@ -948,6 +948,16 @@ wrong before you publish your newly-created tag, you can delete
and recreate it. Once you push your tag, we're stuck with it
and you'll need to use a new version number for your release.
+Verify that your tag is annotated:
+
+ $ git show v5.11.0
+
+The output must look similar to the following:
+
+ tag v5.11.0
+ Tagger: Jesse Vincent <jesse@bestpractical.com>
+ Date: Fri Oct 2 16:29:56 2009 -0400
+
=head3 build the tarball
Before you run the following, you might want to install 7-Zip (the