It will be used to represent various Computer models.

It will be used to create group of Computer.

Acknowledgement can not be displayed without more informations.

Conflicts:
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_conversion_server.xml
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_install_bt5.xml
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_kumofs_server.xml
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_mailhost_configuration.xml
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_memcached_server.xml
	bt5/erp5_promise/PathTemplateItem/portal_alarms/promise_template_tool_configuration.xml
	bt5/erp5_promise/SkinTemplateItem/portal_skins/erp5_promise/Alarm_checkPromiseMailServer.xml
	bt5/erp5_promise/bt/description
	bt5/erp5_promise/bt/revision
	product/ERP5/ERP5Site.py

This runTestSuite uses "python setup.py test" to launch the tests at
a certain folder.

The runTestSuite can upload results using TaskDistribution.

This code is generic enough to be used by others libraries.

The code on ERP5TypeTestSuite is preserved for backward compatibility for
now, until it got updated.

Update now, force the reload of all alarm promises.

Ser periodicity_hour to 0 in addition with "everyday" frequency

Instead raise an exception, try..except to log incapability of resolve the algorithm

Update copyright, license and xml changes on erp5_workflow business template

This exception is required to be used in ZODB due erp5_promise.

The UI created use "Check Consistency" Name in other to keep compatibility with future implementations which are going to use Constraints and checkConsistency API.

In other to keep the promise, create an System Preference if no other were setupped.

Sometimes on configuration product-config can be defined but promise-path and
site id isn't, like for example when some instance use DeadlockDebugger.