Bug#113850: 2.5.0 ETA?

[Earl Hood <earl@earlhood.com>]

--- Jeff Breidenbach <jeff@jab.org> wrote:

> Folks at Debian (including me) are speculating as to when mhonarc
> 2.5.0 might be released and/or whether it makes any sense for Debian
> to ship 2.5.0b2. The question is somewhat influenced by Debian's very
> long release cycle which will roll over within a few months.  So --
> would you be interested in sharing a guesstimated timeline for mhonarc
> releases up to and including 2.5.0?

2.5.0 should be released sometime soon.  There were some recent patches
submitted related to Japanese text processing, and some confirmation
on some items need to be done before 2.5.0 release is done.

> Regardless of Debian's choice, I'm quite happy personally using
> mhonarc 2.5.0b2. Performance seems comparable to 2.4.x series, and
> I've seen no problems so far, and really like the thread slices.

BTW, you may be interested in the following note I added to the
TSLICE docs for 2.5.0:

NOTE  The value of the TSLICE resource is used to determine the number 
      of messages to update, before and after by thread, when a new    
      message is added. To insure that messages within a thread slice  
      are updated when a new message is added, make sure the before and
      after ranges specified for TSLICE is equal to maximum before and 
      the maximum after range arguments specifed in the uses of the    
      $TSLICE$ resource variable. For example, if you have $TSLICE(0;4)$
      and $TSLICE(3;3)$ in message layout resources, you should set  
      TSLICE to 3:4.                                                   
                                                                       
      If you only use $TSLICE$ once, it is best to set options for     
      thread slice formatting via the TSLICE resource so you will not  
      have anything to worry about.                                    

Jeff, I did not notice the above issue until after I sent you a patched
resource file using $TSLICE$.

To summarize the note above: Some message pages may not get properly
updated to reflect changes in $TSLICE$ listing.  This can occur if
the message is more than one message away from a new message in a thread.
I consider it not a major problem since the next/prev links still
function properly.  However, older messages may not properly show the
latest slice representation, and as the reader goes through the thread,
the slice listing can appear to grow as they go from older messages to
newer messages.

--ewh


=====
Earl Hood,
earl@earlhood.com
<http://www.earlhood.com/>

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com