[logon] finally: burn-in tests for the LOGON release

[Stephan Oepen]

dear all,

i believe i have finally managed to take care of the remaining bug  
reports and at least some of the feature requests for this release.  i  
checked in a number of changes last night and would now like to  
‘freeze’ the repository for a final testing phase, i.e. ask  
everyone to abstain from further changes until the release is complete  
(about a week from now).

i also made changes to some of the top-level scripts, hence we should  
now systematically test all core functionality.  could i ask the  
component maintainers to get the latest LOGON ‘trunk’, making sure  
you have no local modifications or unusual user-specific settings, and  
run parsing, transfer, generation, or translation---as are applicable  
to the resource(s) you control.  you should test both interactive and  
batch mode, and i would be grateful if you would email me the batch  
tests (i.e. complete command lines) that you found successful; i will  
then collect these on the wiki, and we can gradually build up a more  
rigorous testing harness.

finally, i also revised the code for on-line web demonstrators,  
rationalizing the controls for exhaustive vs. n-best processing.   
unlike in the past, the software will now try to activate selective  
unpacking where appropriate, which yields potentially better ranking  
and improved efficiency.  could everyone operating a web demo based on  
the LOGON tree please update, reload, and test carefully?

even though we have pursued this release at a leisurely pace so far,  
may i suggest tuesday, 1-sep as the cut-off date for burn-in testing.   
we should probably get this out of our way as soon as we can :-).

with thanks in advance, oe