/*
 * Copyrights     : CNRS
 * Author         : Oleg Lodygensky
 * Acknowledgment : XtremWeb-HEP is based on XtremWeb 1.8.0 by inria : http://www.xtremweb.net/
 * Web            : http://www.xtremweb-hep.org
 * 
 *      This file is part of XtremWeb-HEP.
 *
 *    XtremWeb-HEP is free software: you can redistribute it and/or modify
 *    it under the terms of the GNU General Public License as published by
 *    the Free Software Foundation, either version 3 of the License, or
 *    (at your option) any later version.
 *
 *    XtremWeb-HEP is distributed in the hope that it will be useful,
 *    but WITHOUT ANY WARRANTY; without even the implied warranty of
 *    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *    GNU General Public License for more details.
 *
 *    You should have received a copy of the GNU General Public License
 *    along with XtremWeb-HEP.  If not, see <http://www.gnu.org/licenses/>.
 *
 */


********************************************
*                XWHEP-8.X                 *
*------------------------------------------*
* Release date :                           *
* Author : Oleg Lodygensky                 *
*          lodygens@lal.in2p3.fr           *
* Trac   : https://trac.lal.in2p3.fr/DGHEP *
********************************************


Developments are tracked on our trac server referred above.


* <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
*
*         Major points in this version
*        <---------------------------->
*  - minor bugs corrected
* <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


   Please, see https://trac.lal.in2p3.fr/DGHEP/report/9


-A- Corrections

   Please, see Track_report.html or https://trac.lal.in2p3.fr/DGHEP/report/9

-B- New features

   Please, see Track_report.html or https://trac.lal.in2p3.fr/DGHEP/report/9

-C- Known Bugs

-C.1- xtremweb.gmond.pl does not scale
-C.2- the scheduler is not fair
-C.3- 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.