Preparing a release

5 files changed, 12 insertions, 17 deletions

diff --git a/ChangeLog b/ChangeLog
index e427fd560..e818baf0b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2005-07-26  Werner Koch  <[email protected]>
+
+	Released 1.4.2.
+
 2005-07-20  David Shaw  <[email protected]>
 
 	* configure.ac: Add a define for FAKE_CURL.
diff --git a/NEWS b/NEWS
index 467fffb73..44fb5a573 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-Noteworthy changes in version 1.4.2
+Noteworthy changes in version 1.4.2 (2005-07-26)
 ------------------------------------------------
 
     * New command "verify" in the card-edit menu to display
diff --git a/configure.ac b/configure.ac
index e6637a3d5..ef9370089 100644
--- a/configure.ac
+++ b/configure.ac
@@ -26,7 +26,7 @@ min_automake_version="1.9.3"
 
 # Remember to change the version number immediately *after* a release
 # and remove the "-cvs" or "rc" suffix immediately *before* a release.
-AC_INIT(gnupg, 1.4.2-cvs, [email protected])
+AC_INIT(gnupg, 1.4.2, [email protected])
 # Set development_version to yes if the minor number is odd or you
 # feel that the default check for a development version is not
 # sufficient.
diff --git a/g10/import.c b/g10/import.c
index 0953ade44..8c96e5a6a 100644
--- a/g10/import.c
+++ b/g10/import.c
@@ -625,8 +625,7 @@ check_prefs(KBNODE keyblock)
 	}
     }
 
-#warning DEBUG CODE ENABLED
-  if(problem || getenv ("FOOBAR"))
+  if(problem)
     {
       log_info(_("it is strongly suggested that you update"
 		 " your preferences and\n"));
diff --git a/scripts/mail-to-translators b/scripts/mail-to-translators
index 23ee4be58..7aac1606b 100755
--- a/scripts/mail-to-translators
+++ b/scripts/mail-to-translators
@@ -35,25 +35,17 @@ Content-Type: multipart/mixed; boundary="=-=-="
 
 Hi!
 
-We are preparing for the 1.4 release of GnuPG and like you to ask to
-start with the translation.  The recent release 1.3.91
-(ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.91.tar.bz2) won't be
-the last one before 1.4 and experience has shown that we will still
-need to change some strings on the way to 1.4.  However due to a lot
-of fuzzy entries and about 110 new strings it would be good to start
-translating right now but wait with sending the translation back.  We
-will tell when we think that we are ready and provide a new POT file
-for merging with your current translation.
+We are preparing for a new 1.4 release of GnuPG and like you to ask to
+update your translation. 
 
 Please find attached the very latest version of the PO file for your
-GnuPG translation ($file) from 1.3.91.
+GnuPG translation ($file).
 
 IMHO it is important to have a basic understanding of GnuPG's
 functionality to do a correct translation.  A false translation might
 lead to security problems.  Furthermore the TP Robot is not able to
-handle more than one version of a project (we have 1.2, 1.3 and also
-1.9) and thus I'd ask you *not to use the TP Robot* for 1.3.x or
-1.4.x.
+handle more than one version of a project (we have 1.2, 1.4 and also
+1.9) and thus I'd ask you *not to use the TP Robot* for GnuPG. 
 
 Output of msgfmt is:
 $(msgfmt --check --statistics $file 2>&1 | head)