security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

build: Update README.maint.

Browse source 
--
Also fixed some typos.
This commit is contained in:
Werner Koch 2014-11-05 08:42:56 +01:00
parent b453226f56
commit 6b54759976
2 changed files with 20 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.maint
View file

@ -23,10 +23,7 @@ Release process:
* Decide whether you want to update the automake standard files
(Mainly config.guess and config.sub).
* [1.4 only] Update gpg.texi and gpgv.texi from master:
make -C doc update-source-from-gnupg-2
* [1.4 and 2.0] Copy needed texinfo files from master:
* [2.0] Copy needed texinfo files from master:
make -C doc update-source
* Run:
@ -34,11 +31,9 @@ Release process:
* Write NEWS entries and set the release date in NEWS.
* [1.4 and 2.0] In configure.ac set "my_isgit" to "no".
* Commit all changes to GIT with a message of "Release n.m.o."
* Tag the revision with the string "gnupg-x.y.z".
* Create a signed tag with the name "gnupg-x.y.z".
* Run "./autogen.sh --force"
(--force is required for the git magic in configure.ac and a good
@ -64,11 +59,12 @@ Release process:
* Copy the files to the FTP server
* Update the webpages - at least the file swdb.wml needs an update.
* Update the webpages - at least the file swdb.mac needs an update.
* Add a new headline to NEWS.
* Bump "my_version" up and set "my_isgit" back to "yes" in configure.ac
* Bump the version number in configure.ac up, add an empty NEWS
entry, commit, and push that.
* Write an announcement.