Add reminder about uploading public key to keys.gnupg.net.

* HACKING (Release Procedure): Here.
(cherry picked from commit 06c3084fb5)
This commit is contained in:
Joel E. Denny
2009-02-03 03:08:32 -05:00
parent c1455babda
commit 015e86a7b2
2 changed files with 14 additions and 3 deletions

View File

@@ -1,3 +1,8 @@
2009-02-03 Joel E. Denny <jdenny@ces.clemson.edu>
Add reminder about uploading public key to keys.gnupg.net.
* HACKING (Release Procedure): Here.
2009-03-31 Akim Demaille <demaille@gostai.com>
bootstrap: --help to stdout.

12
HACKING
View File

@@ -257,9 +257,15 @@ The generic GNU upload procedure is at:
http://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads
After following the instructions there to register your information so you're
permitted to upload, here's a brief reminder of how to roll the tarballs and
upload them:
Follow the instructions there to register your information so you're permitted
to upload. Make sure your public key has been uploaded at least to
keys.gnupg.net. You can upload it with:
gpg --keyserver keys.gnupg.net --send-keys F125BDF3
where F125BDF3 should be replaced with your key ID.
Here's a brief reminder of how to roll the tarballs and upload them:
*** make distcheck
*** gpg -b bison-2.3b.tar.gz