mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
Switch to the new automagic beta numbering scheme.
* configure.ac: Add all the require m4 magic. -- This also removes the hack to allow custom version numbers which are not considered a development version. A custom version number can be done anyway by simply setting the version to it and tag the release with it.
This commit is contained in:
parent
b4d9f8dbc8
commit
68777b40dc
2 changed files with 28 additions and 36 deletions
|
@ -34,12 +34,14 @@ Release process:
|
|||
|
||||
* Write NEWS entries and set the release date in NEWS.
|
||||
|
||||
* In configure.ac set "my_isgit" to "no".
|
||||
* [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".
|
||||
|
||||
* Run "./autogen.sh --force"
|
||||
(--force is required for the svn magic in configure.ac and a good
|
||||
(--force is required for the git magic in configure.ac and a good
|
||||
idea in any case)
|
||||
|
||||
* Run "configure --enable-maintainer-mode".
|
||||
|
@ -58,8 +60,7 @@ Release process:
|
|||
You might need to set a different signature key than mine. mkdiff
|
||||
has an option for this.
|
||||
|
||||
* If you are satisfied with the result commit a tag for the release
|
||||
and push the changes.
|
||||
* Push the git changes and the tag.
|
||||
|
||||
* Copy the files to the FTP server
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue