This BT contains the same category twice.

Bank Account, Currency{, Module}, Currency Exchange {Cell,Line} already
exist in erp5_base, which is a dependency of this Business Template at
least through erp5_trade.
"composition" and "variation" Base Categories exist in erp5_pdm, which
is a dependency of this Business Template via erp5_trade.
"site" Base Category exists in erp5_base, which is a dependency of this
Business Template via erp5_trade.

classification is already provided by erp5_dms, which is a dependency
of this BT already.

requirement is also present in erp5_project. So add a dependency on that BT
and remove the duplication.

This BT achieved the rare feat of containing the same document twice.

region/europe/western_europe is also present in erp5_tiosafe_test, which is
already installed in the same unit test. So add a dependency on that BT and
remove the duplication.

currency_module/euro is also present in erp5_tiosafe_test, which is already
installed in the same unit test. So add a dependency on that BT and remove
the duplication.

Vincent Pelletier:
- Disable timeout by default.

Vincent Pelletier:
- Ignore TimerService-originated publication requests.
- Add copyright headers.
- Disable timeout by default.
- Give a meaning to requested negative deadlines.
- Docstrings.
- Assorted simplifications.

The Assigments are only relevant if the User is based on Person Document, on SlapOS, an user come from a Computer or a Software Instance Document. This change makes the document compatible with other kinds of Users, as Assigment is overkill for Non-Person cases, as the presence of ERP5 Login is enough to determinate the User existence. 

The other alternative would be re-factorize to not duplicate code, which seems not the intention of how this code was written. 

/cc @jerome, @kazuhiko 



/reviewed-on nexedi/erp5!458

Simpler, and reduces the exposure of exc_info (which can be tricky to use
in other contexts).

Unlike Medusa, WSGI does not do it.

Both the dummy method_id and the actually-used grouping_method_id.

Without this commit, it felt back to the timerserver egg.

HAL JSON uses JSON, which uses UTF-8, but properties of ERP5 documents
does not enforce any specific encoding, so if we happen to have
documents with string properties that are not UTF-8 compatible, they
could not be queried with HAL JSON (json.dumps was raising UnicodeError)

This pre-process field default properties and document title to make
sure they can be serialized as json. This assumes that configuration
(form definition, actions, ...) will be valid UTF-8, but just does extra
effort to make sure "broken" data can be displayed without error.

/reviewed-on nexedi/erp5!928

ZODB Components: 'Migrate Components from Filesystem to ZODB' view: Fix ListBox to display selected ones first.

In this context, 'selected' means classes found by introspecting Portal Type
Class MRO. This was not sorted properly only for filesystem Products.

ZODB Components: Do not automatically validate when importing from FS as imports have to be adjusted manually.

Besides not being actually needed, checkPythonSourceCode() was called on all
temp_objects created for migrate_component_from_filesystem Business Template Action.

/reviewed-on nexedi/erp5!929

['Person: 372 doc/hour; SaleOrder: 132 doc/hour;']
Thus adjust accordingly. Do not mix http and https.

/reviewed-on nexedi/erp5!926

Editing instance parameters will automatically trigger instance update at node and there's no need to stop / start instance.

evaluated before timeout and thus causing unexpected AttributeErrors
later.

password pair generated (in some cases this might happen after frontend
generation leading to 403 HTTP error codes in bootstrap code.)

Cleanup conditional code.