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

Difference between revisions of "Beta Versions"

(Changelog)
(Added 6.0.0-beta1, 4.4.5-rc1 and 4.3.8-rc1 releases)
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 (6.0.0-beta1)=
  
 
The source can be downloaded from:
 
The source can be downloaded from:
  
  
ftp://ftp.hylafax.org/source/BETA/hylafax-4.3.2rc1.tar.gz
+
ftp://ftp.hylafax.org/source/testing/hylafax-6.0.0-beta1.tar.gz
  
  
Line 18: Line 18:
 
==New features of particular note==
 
==New features of particular note==
  
===Template-based email notifications===
+
HylaFAX 6.0 introduces several new features for HylaFAX, building on the strong
 +
history of innovation:
 +
* PCL Support
 +
* hfaxd can sort list output (like sendq) arbitrarily for clients
 +
* I18n: HylaFAX client strings are now translated and available in different languages
 +
* IPv6 support
 +
* New permissions in hfaxd to allow for more admin control on who can see/modify jobs/faxes (see PublicJobQ/JobProtection/PublicRecvQ)
 +
* Powerful page range handling capabilities
 +
* Better faxq/notify integration
 +
* as well as many improvements to the T.30 protocol code.
  
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.
+
The one notable change if you're upgrading from HylaFAX 4.4 or older is that
 +
the old protocol is no longer supported.  This will only affect you if you've
 +
been using a client that uses the old protocol and hasn't been updated to use
 +
the normal FTP-style HylaFAX protocol.
  
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.
+
==Changelog==
  
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).
+
A complete list of changes since HylaFAX 4.4 was branched off for stable maintenance is available in the [http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-6.0.txt;hb=master HylaFAX 6.0 release notes]
  
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):
+
=Current stable branches release candidates=
  
etc/templates/$TEMPLATE/<template name>
+
These releases are maintenance releases, and do not contain any new
 +
features or functionality, but only contain bugfixes.
  
So, with TEMPLATES unset, you get the default templates.  If TEMPLATES=fr, you would use the templates in:
+
There currently are release candidates for the following stable branches:
  
etc/templates/fr/<template name>
 
  
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.5-rc1 [ [ftp://ftp.hylafax.org/source/testing/hylafax-4.4.5-rc1.tar.gz Source] ] [ [http://git.hylafax.org/HylaFAX?a=blob;f=doc/RELEASENOTES-4.4.txt;hb=HYLAFAX-4_4-branch Release Notes] ]
  
Templates are of the format:
+
4.3.8-rc1 [ [ftp://ftp.hylafax.org/source/testing/hylafax-4.3.8-rc1.tar.gz Source] ] [ [http://git.hylafax.org/HylaFAX?a=blob;f=CHANGES;hb=HYLAFAX-4_3-branch 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 4.4.4/4.3.7 is as follows:
  
* Encode subject headers (using B encoding) when necessary (9 Feb 2007)
+
* Fix faxq modem triggers (4.3 & 4.4)
* Added sample HTML templates to demonstrate templating features (9 Feb 2007)
+
* hfaxd lockJob() - don't blindly O_CREAT job we're trying to lock (4.3 * & 4.4)
* Added error exit codes to faxinfo (7 Feb 2007)
+
* hfaxd: Don't update job's last modified time unless it's actually successful (4.3 & 4.4)
* PAM reworked to use complete sessions independantly (25 Jan 2007)
+
* faxq: Be more careful in choosing jobs to batch (4.3 & 4.4)
* Added debian/ directory with rules to create a simple Debian package (21 Jan 2007)
+
* hfaxd: Fix RECV_START, RECV_PAGE, RECV_DOC triggers (4.3 & 4.4)
* Simplify/Unify mime encoder selection and use (9 Jan 2007/29 Jan 2007)
+
* faxgetty/faxsend: Correct Include config file parsing (4.3 & 4.4)
* Add the Include: option for Config file options (8 Jan 2007)
+
* Bug 901: mimeencoding bug in templates handling (4.3 & 4.4)
* Redirected unwanted output from pd2pdf while running notify (24 Dec 2006)
+
* Abort receive session on error writing to file (4.4)
* Use @SCRIPT_SH@ for bin/ scripts to allow configure selection (23 Dec 2006)
 
* Updated pollrcvd to use templates (22 Dec 2006)
 
* Moved default templates to etc/tempates/en/ to clean up etc/templates/ (22 Dec 2006)
 

Revision as of 21:24, 6 March 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 (6.0.0-beta1)

The source can be downloaded from:


ftp://ftp.hylafax.org/source/testing/hylafax-6.0.0-beta1.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.


New features of particular note

HylaFAX 6.0 introduces several new features for HylaFAX, building on the strong history of innovation:

  • PCL Support
  • hfaxd can sort list output (like sendq) arbitrarily for clients
  • I18n: HylaFAX client strings are now translated and available in different languages
  • IPv6 support
  • New permissions in hfaxd to allow for more admin control on who can see/modify jobs/faxes (see PublicJobQ/JobProtection/PublicRecvQ)
  • Powerful page range handling capabilities
  • Better faxq/notify integration
  • as well as many improvements to the T.30 protocol code.

The one notable change if you're upgrading from HylaFAX 4.4 or older is that the old protocol is no longer supported. This will only affect you if you've been using a client that uses the old protocol and hasn't been updated to use the normal FTP-style HylaFAX protocol.

Changelog

A complete list of changes since HylaFAX 4.4 was branched off for stable maintenance is available in the HylaFAX 6.0 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:


4.4.5-rc1 [ Source ] [ Release Notes ]

4.3.8-rc1 [ 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 4.4.4/4.3.7 is as follows:

  • Fix faxq modem triggers (4.3 & 4.4)
  • hfaxd lockJob() - don't blindly O_CREAT job we're trying to lock (4.3 * & 4.4)
  • hfaxd: Don't update job's last modified time unless it's actually successful (4.3 & 4.4)
  • faxq: Be more careful in choosing jobs to batch (4.3 & 4.4)
  • hfaxd: Fix RECV_START, RECV_PAGE, RECV_DOC triggers (4.3 & 4.4)
  • faxgetty/faxsend: Correct Include config file parsing (4.3 & 4.4)
  • Bug 901: mimeencoding bug in templates handling (4.3 & 4.4)
  • Abort receive session on error writing to file (4.4)


Powered by MediaWiki
Attribution-ShareAlike 2.5

Project hosted by iFAX Solutions