PoC inclusion of Alarm errors on ERP5. So you don't need to rely on email notification to know some alarm has execution error.

   For now it just browse all enabled (using alarm_date not None), but in future, we could include a more narrow scope.

  otherwise this becomes unusable whenever a project has custom set of categories

See merge request !2064

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

  'Just' a typo

   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