4.2.3 is born. Great work all! -d

diff --git a/CHANGES b/CHANGES
index 290088ddaf87953a573dec1a15c38e5fb7d5a160..8c917577d8929b249a1eabcb106d1fae6da8af57 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,6 +1,6 @@
 #      $Id$    
 
-Changelog for HylaFAX 4.2.3rc1
+Changelog for HylaFAX 4.2.3
 
 * fix clients to accept 1yz preliminary reponse on connection
   according to RFC959 (8 Nov 2005)

diff --git a/README b/README
index 9e03765754972a663a5bfcdbb0d6b9d3ddd762b3..a2b31a4d75af5c2b90a5b7e96b11e437d4e23e1e 100644 (file)
--- a/README
+++ b/README
@@ -2,23 +2,23 @@ $Id$
 
                            *   ANNOUNCE   *
 
-The HylaFAX development team is pleased to announce our 4.2.2
+The HylaFAX development team is pleased to announce our 4.2.3
 patch level release!  As always, our sincerest thanks go to all who
 participate and provide feedback.
 
                                *   *   *
 
 This document is intended to describe the significant differences
-between hylafax-4.2.2 and older releases, point out any known
+between hylafax-4.2.3 and older releases, point out any known
 incompatibilites and issues, and provide the reader with directions to
 further resources regarding HylaFAX. 
 
                           *   NEW FEATURES   *
 
-* faxgetty can now utilize more than two call identification tags
-* color fax (JPEG) reception is now supported (requires updating
-  libtiff and libjpeg)
-* FaxModify makes pre-processing outbound fax images on the server easier
+* IXO/TAP page batching
+* JBIG send support via ModemSoftRTFCC in Class 1/1.0 (requires
+  JBIG-KIT library)
+* Retransmit-Ignore, a new RTNHandlingMethod, is now the default
 * numerous other enhancements and bugfixes (see CHANGES)
 
                          *   KNOWN ISSUES   *
@@ -31,29 +31,21 @@ further resources regarding HylaFAX.
   prototypes may contain Class1TCFRecvHack.  This is no longer desireable
   for production use, and this feature should now only be used for
   debugging purposes.
-* Some of the CallID changes in this release required some reordering of
-  the command-line parameters with which the DynamicConfig scripts were
-  called.  If you use DynamicConfig check your scripts after upgrading.
-* TIFFs received prior to upgrading to this release will display their
-  CIDName and CIDNumber information reversed (CallID2, CallID1) when
-  examined with faxinfo.
+* If upgrading from any release other than 4.2.2 directly, be advised that
+  CIDName/CIDNumber are now part of a larger CallID framework. 
 * libtiff-3.6.1 is fatally flawed when dealing with Group 3 images.  
   Don't use it as-is.  
   See: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=500
 
                       *   WHO SHOULD UPGRADE?   *
 
-* For security reasons, everyone not yet using 4.2.1 should consider
-  upgrading to this 4.2.2 release as soon as possible.
-* New improvements in 4.2.2 with unexpected signal handling should benefit
-  most Class 1/1.0 users (with or without ECM enabled).
-* If using a modem with a newer Rockwell or Conexant chipset that
-  indicates Class 1.0 support you may want to upgrade and re-run faxaddmodem
-  to choose Class 1.0 in order to improve unexpected signal handling.
-* If you regularly send fax batches (new in 4.2.0) you should upgrade to
-  get the fixes in 4.2.2.
-* If you wish to send multipage faxes with mixed page lengths you should
-  upgrade (requires patching Ghostscript).
+* For security reasons, everyone should consider upgrading to this 4.2.3
+  release as soon as possible.
+* Users of Class 1/1.0 devices should upgrade to benefit from ongoing
+  work in this area  
+* Users who regularly send fax batches (first introduced in 4.2.0) 
+  should upgrade to get the fixes in 4.2.3.
+
 
                      *   HYLAFAX BINARY PACKAGES   *
 

diff --git a/VERSION b/VERSION
index e0efc26e709eb165e5462b6430bf36ce5ca42daa..f2c6cb6af20f460be7d4b1f12a4cbe216a103535 100644 (file)
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-4.2.3rc1
+4.2.3