This make everything slow as hell and prevent to quickly save.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

erp5_web_renderjs_ui: keep previous focus color

If user group are recalculated before changing the workflow state, it will only return the same security group
See nexedi/erp5@c00c3636

Accounts with a balance that is not 0 in transaction currency
(quantity) and 0 in accounting currency (asset price) were not correctly
indexed in balance transactions.
The visible problem was that every year the amount in local currency for
this account was doubled - while the amount in accounting currency
remainded 0, making this problem not so impactful.

When an invoice has a resource set, newly added invoice lines and cells
will lookup prices using currency exchange lines (and might even find
a price).

uninstalling a ModuleTemplateItem containing document is usually not
what people want, so the default option should be to keep.

See merge request !2063

Commit a01da084 failed to fix the
handling of parameters in the dealShebang function and the bug is now
triggered since slapos@f834a06f:

$ PATH=...  SLAPOS_TEST_LOG_DIRECTORY=... SLAPOS_TEST_SHARED_PART_LIST=... /bin/sh '-e
' /srv/slapgrid/slappart0/t/.../i/0/bin/runTestSuite ...
runTestSuite: /bin/sh: 0: Illegal option -

The script now has a drop-in replacement in `erp5_trade` which works as-is even
in the case of advanced trade (calls `Movement_isQuantityEnabled`). Henceforth,
the custom script in `erp5_advanced_trade` is not needed anymore.

The two scripts were a bit too independant from one another, sometimes causing
weird behaviours. Editing a quantity now depends on the quantity being enabled,
which happens when the line is not expected to have cells or sublines.

Also enforces expected behaviour for items: if a product or service has
*required* items, its quantity cannot be edited, since quantity of the items
should set the quantity of the line or cell.

New year does not mean the period is 365 days.

See merge request !2057

   The alarm was replaced by a proper CodingStyle test. Fixit is incoherent since you need to edit/custom it to adjust the cache plugin for each use case.

   Rely on test result is just fine for this purpose.

  API changed for Pdb() call after 8.0.0rc1 release.

See merge request !2046

See merge request !2055

we mainly add a Quality Assurance Module, which mainly contains: Quality Control, Gate, Traceability, SMON, ACOM

Quality Control: Present a quality control, such as validate document
Gate: when a gate is posted, the quality element which's int index is greater than this one and smaller than next gate will change to Expected state
Traceability: used to record the informations of products used
SMON: it's like a Gate, when validate, the product is off of fabrication line
ACOM: all controls are finished, manufacturing execution is finished

The Quality Element has a Quality Assurance Workflow workflow described as blow
Draft -> Creation State
Queued -> Document is planned, wait to show to the user
Expected -> Document is shown to the user for it to be completed
Pending Update -> A version of this document has been posted that doesn't satisfy Quality Assurance. A New version is needed. (useful for Quality Operation that needs to be redone). Document is shown to the user for it to be completed.
Posted -> Document has been completed by the user.
Archived -> A new version of the document has been posted, the old one become archived
it has also a Quality Assurance Interaction Workflow which is used to show next /archive previous  quality element

it's a regression introduced by 1b555dbf

in ManufacturingOrder_view and ManufacturingExecution_view, we have a field Ledger,so probably we miss this category in builder

erp5_site_global_id was from the tiolive time, when we were using ERP5
with mariadb and memcached instances shared by many zope instances, this
was used as a way to implement namespaces in memcached, to prevent
conflicts such as two different zope using the same cache keys.

Nowadays, we no longer share memcached, each ERP5 instance has its own
memcached and this prefixing is no longer needed, but there is still one
exception, when we run test using runTestSuite with --node_quantity
higher than 1, we have multiple running test instances sharing the same
mariadb and the same memcached. In that case, each test instance
uses a different mariadb database, but the risk of conflict remain for
memcached.

To solve this, we introduce a prefix for keys, choosen randomly at test
startup.

This was more or less what the current implementation was trying to do,
but we were setting erp5_site_global_id on the wrong object, so it was
not working since 4889d523 (Define property's default value at class
level., 2012-12-31). Also, this was only done at the level of SharedDict,
but some APIs such as CacheTool or SessionTool use MemcachedDict
directly. There was other problems that using the sql connection string
encoded in base64 was a too long prefix, because memcached are limited
in size. Also it was not preventing collisions when running tests on
the same test node, each runUnitTest execution was still having
pollution from the previous runUnitTest.

This does not validate against the schema:

   Element 'ecriture': Missing child element(s). Expected is ( ligne ).