***********************************
*           XWHEP-7.4.1           *
*---------------------------------*
* Release date :  May 13th, 2011  *
* Author : Oleg Lodygensky        *
*          lodygens@lal.in2p3.fr  *
***********************************



-A- Corrections
-A.1- worker, server: xtremwebconf.sh corrected ('status' param now accepted)
-A.2- worker, server: launching services do not display any more "ls: *.zip: No such file or directory"
-A.3- worker, server : log files are now stored in /var/log
-A.4- server : a bug corrected on DB cache usage
-A.5- client : a bug corrected on xwversion command
-A.6- client : a message is now displayed if config file not found
-A.7- client : the config file is not modified since it appeared to be too confusing for the user
-A.8- works and datas tables modified as needed for the 3G bridge plugin : label and name set to char(150)
-A.9- a bug corrected on group jobs management


-B- New features


-C- Known Bugs

-C.1- Result download errors reported using 'xwdownload', but not with 'xwresult'
  We have not been able to reproduce them
  If you encounter these, please send us log file in DEBUG mode
-C.2- xtremweb.gmond.pl does not scale
-C.3- windows 7 not supported
-C.4- the scheduler is not fair
-C.5- there may be some concurrent access problems leading to some errors
      There may be two concurrent accesses problems
        - on server side, DB access may lead to inconsistency between works and tasks tables
	  This could certainly be solved using SQL transactions
	  But we would then need MySQL >=5
	  There are sime issues withe transactions with hsqldb
	- on worker side, file access if a worker is configured to run jobs in parallel (default one thread per CPU core)

	We have observed that these concurrent access problems may lead to up to 6% erroneous jobs.
	Until further notification, we consider this rate acceptable.


- Versionning -

Versionning is as follow
	- X is a major part of the version
	- Y is a minor part of the version
	- Z is the micro part of the version

(*) X reports a very important change : for example the communication protocol changes or a major new feature is modified/introduced/removed
When X changes, backward compatibility is not ensured

(*) Y reports a important but not critical change : backward compatibility is ensured

(*) Z reports a minor change : bug correction, documentation changes etc.