Personal tools
HylaFAX The world's most advanced open source fax server

Difference between revisions of "Beta Versions"

(Changelog)
(Updated for newest stable branch release candidates)
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
=Reporting Bugs=
 
=Reporting Bugs=
The HylaFAX Bugzilla is located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. Please file a bug report there if you can. If you prefer to send a message to the mailing lists to discuss the problem, we encourage you to subscribe to hylafax-devel@hylafax.org and post it there. The hylafax-users mailing list will also reach many of the right people, and is the next best thing if subscribing to -devel and filing a bug report seem like too much trouble. Bottom line - we want your bugs!!
+
The HylaFAX Bugzilla is located at [http://bugs.hylafax.org/ http://bugs.hylafax.org/]. Please file a bug report there if you can. If you prefer to send a message to the [[Mailing Lists]] to discuss the problem, we encourage you to subscribe to hylafax-devel@hylafax.org and post it there. The hylafax-users mailing list will also reach many of the right people, and is the next best thing if subscribing to -devel and filing a bug report seem like too much trouble. Bottom line - we want your bugs!!
  
  
=Current release candidate (4.3.2rc1)=
+
=Current release candidate=
 
 
The source can be downloaded from:
 
 
 
 
 
ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.2rc1.tar.gz
 
 
 
 
 
Please refer to our [[Red_Hat_Packages]] page for a source RPM that should build on most Red Hat, Fedora and SuSE distributions.
 
  
 +
There is no current release candidate for the development branch.
  
 
==New features of particular note==
 
==New features of particular note==
  
===Template-based email notifications===
+
None yet.
  
In the past, there has been discussion about both customizing and translating the e-mails that faxrcvd and notify send. In this version of HylaFAX, we've done some work to make faxrcvd and notify use "templates" for their e-mail messages.
+
==Changelog==
  
This means that faxrcvd and notify no longer use the "bin/dictionary" and eval "echo $..." everywhere when creating their e-mails, but now directly use a template file.
+
A complete list of changes since HylaFAX 6.0 was branched off for stable maintenance is available in the [http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-GIT.txt;hb=master HylaFAX GIT release notes]
  
These versions continue the tradition of sourcing etc/FaxDispatch (for faxrcvd) and etc/FaxNotify (for notify) to get "command" variables that influence what they do.  Of course, these shell scripts can continue to do whatever else they were doing (including calling exit to terminate normal faxrcvd/notify handling if desired).
+
=Current stable branches release candidates=
  
These shell scripts can now also set the TEMPLATE variable to control the source of template files that faxrcvd/notify use to generate their e-mails.  Templates are taken from (relative $SPOOL, where notify/faxrcvd are run from):
+
These releases are maintenance releases, and do not contain any new
 +
features or functionality, but only contain bugfixes.
  
etc/templates/$TEMPLATE/<template name>
+
There currently are release candidates for the following stable branches:
  
So, with TEMPLATES unset, you get the default templates.  If TEMPLATES=fr, you would use the templates in:
 
  
etc/templates/fr/<template name>
+
6.0.4-rc2 [ [ftp://ftp.hylafax.org/source/testing/hylafax-6.0.4-rc2.tar.gz Source] ] [ [http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-6.0.txt;hb=6.0 Release Notes] ]
  
We've created a basic set of templates, and a set of translations of them, based on our reading and knowledge of the current faxrcvd and notify scripts. We're sure there are problems with some of the templates, so corrections are welcome.
+
4.4.6-rc2 [ [ftp://ftp.hylafax.org/source/testing/hylafax-4.4.6-rc2.tar.gz Source] ] [ [http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-4.4.txt;hb=4.4 Release Notes] ]
  
Templates are of the format:
+
4.3.9-rc2 [ [ftp://ftp.hylafax.org/source/testing/hylafax-4.3.9-rc2.tar.gz Source] ] [ [http://git.hylafax.org/HylaFAX?a=blob;f=CHANGES;hb=4.3 Release Notes] ]
  
<pre>
 
From: FAX Agent <$FROMADDR>
 
Subject: Fax received from "$SENDER"
 
Content-type: text/plain; charset=us-ascii
 
  
$FILE (ftp://$HOSTNAME:4559/$FILE):                                 
+
Please refer to our [[Red_Hat_Packages]] page for a source RPM that should build on most Red Hat, Fedora and SuSE distributions.
  Sender: $SENDER
 
  Pages: $PAGES
 
Quality: $QUALITY
 
    Size: $PAGE
 
Received: $RECEIVED
 
Time To Receive: $TIMETORECV
 
    Signal Rate: $SIGNALRATE
 
    Data Format: $DATAFORMAT
 
  Error Correct: $ERRCORRECT
 
CallID1: $CALLID1
 
CallID2: $CALLID2
 
    Received On: $DEVICE
 
  CommID: $COMMID (ftp://$HOSTNAME:4559/log/$COMMID)     
 
</pre>
 
 
 
Templates are 2 sections, separated by a blank line.  The "header" section is included in the headers of the e-mail.  So the template can actually specify the content-type it is, including any charset, etc.
 
 
 
This means that you *can* make your template something like:
 
 
 
<pre>
 
From: ...
 
Subject: ...
 
Content-type: text/html
 
  
<html>
 
<body>
 
  <table>
 
  <tr><td>Sender:</td><td>$SENDER</td></tr>
 
  ....
 
</body>
 
</html>
 
</pre>
 
  
 
==Changelog==
 
==Changelog==
  
A complete list of changes since 4.3.1 is as follows:
+
A complete list of changes since 6.0.3/4.4.5/4.3.8 is as follows:
  
* Encode subject headers (using B encoding) when necessary (9 Feb 2007)
+
* Class1: ECM page and block count should be sent as modulus. (4.3, 4.4, 6.0)
* Added sample HTML templates to demonstrate templating features (9 Feb 2007)
+
* faxsend: Class1 1 ECM when skipping pages needs to be more careful (6.0)
* Added error exit codes to faxinfo (7 Feb 2007)
+
* Class1: Initialize blockNumber (4.3, 4,4)
* PAM reworked to use complete sessions independantly (25 Jan 2007)
+
* hfaxd: log what address(es) we're listing on when starting (6.0)
* Added debian/ directory with rules to create a simple Debian package (21 Jan 2007)
+
* Update releasenotes and documentation re IPv6 support (6.0)
* Simplify/Unify mime encoder selection and use (9 Jan 2007/29 Jan 2007)
+
* hfaxd:  Cleanup uid initialization and theoretical overflow (4.3, 4.4, 6.0)
* Add the Include: option for Config file options (8 Jan 2007)
+
* Class1: Initialize blockNumber (4.3, 4,4)
* Redirected unwanted output from pd2pdf while running notify (24 Dec 2006)
+
* Str::vformat()  Don't reuse va_args (4.3, 4.4, 6.0)
* Use @SCRIPT_SH@ for bin/ scripts to allow configure selection (23 Dec 2006)
+
* PageHandling:  Fix handling of large blank areas (4.3, 4.4, 6.0)
* Updated pollrcvd to use templates (22 Dec 2006)
+
* faxq: Don't assert on bad FIFO messages (4.3, 4.4, 6.0)
* Moved default templates to etc/tempates/en/ to clean up etc/templates/ (22 Dec 2006)
+
* Page sent protocol trace fixes (6.0)
 +
* Don't duplicate any file in a release tarball (6.0)
 +
* IPv6: Rework initial bind (6.0)
 +
* Some CVS-GIT cleanups/release notes (6.0)
 +
* pagesend: Fix broken switch statement (6.0)
 +
* nls: Add German translation (6.0)
 +
* Add support for libtiff 3.9 (6.0)
 +
* Updated RPM dependencies (6.0)

Latest revision as of 20:52, 18 December 2009

The HylaFAX development team often asks other developers and interested HylaFAX users to test upcoming software releases. As these are beta versions of software they may contain more bugs than usual, and should probably not be used on production servers if your job depends on the performance of that server!

Reporting Bugs

The HylaFAX Bugzilla is located at http://bugs.hylafax.org/. Please file a bug report there if you can. If you prefer to send a message to the Mailing Lists to discuss the problem, we encourage you to subscribe to hylafax-devel@hylafax.org and post it there. The hylafax-users mailing list will also reach many of the right people, and is the next best thing if subscribing to -devel and filing a bug report seem like too much trouble. Bottom line - we want your bugs!!


Current release candidate

There is no current release candidate for the development branch.

New features of particular note

None yet.

Changelog

A complete list of changes since HylaFAX 6.0 was branched off for stable maintenance is available in the HylaFAX GIT release notes

Current stable branches release candidates

These releases are maintenance releases, and do not contain any new features or functionality, but only contain bugfixes.

There currently are release candidates for the following stable branches:


6.0.4-rc2 [ Source ] [ Release Notes ]

4.4.6-rc2 [ Source ] [ Release Notes ]

4.3.9-rc2 [ Source ] [ Release Notes ]


Please refer to our Red_Hat_Packages page for a source RPM that should build on most Red Hat, Fedora and SuSE distributions.


Changelog

A complete list of changes since 6.0.3/4.4.5/4.3.8 is as follows:

  • Class1: ECM page and block count should be sent as modulus. (4.3, 4.4, 6.0)
  • faxsend: Class1 1 ECM when skipping pages needs to be more careful (6.0)
  • Class1: Initialize blockNumber (4.3, 4,4)
  • hfaxd: log what address(es) we're listing on when starting (6.0)
  • Update releasenotes and documentation re IPv6 support (6.0)
  • hfaxd: Cleanup uid initialization and theoretical overflow (4.3, 4.4, 6.0)
  • Class1: Initialize blockNumber (4.3, 4,4)
  • Str::vformat() Don't reuse va_args (4.3, 4.4, 6.0)
  • PageHandling: Fix handling of large blank areas (4.3, 4.4, 6.0)
  • faxq: Don't assert on bad FIFO messages (4.3, 4.4, 6.0)
  • Page sent protocol trace fixes (6.0)
  • Don't duplicate any file in a release tarball (6.0)
  • IPv6: Rework initial bind (6.0)
  • Some CVS-GIT cleanups/release notes (6.0)
  • pagesend: Fix broken switch statement (6.0)
  • nls: Add German translation (6.0)
  • Add support for libtiff 3.9 (6.0)
  • Updated RPM dependencies (6.0)

This page was last edited on 18 December 2009, at 20:52.

Powered by MediaWiki
Attribution-ShareAlike 2.5

Project hosted by iFAX Solutions