[FIX] account: do not duplicate analytic lines on analytic journal duplicate
[FIX] Avoid access error on XML id in browse when choosing picking type for manual purchase order.  As they are ordered by sequence, just take the first you can find.
[FIX] website_forum: load js files in the right order.
[FIX] point_of_sale: fix point of sale sequence declaration, github issue #3218
[IMP] point_of_sale: make the sequence field configurable
[FIX] project: access rights and followers

For privacy_visibility 'followers' or 'portal', the user should be follower of the project (not the task).
Remove public access to portal task
Fixes #2372

If no project on the task (or other rule), an employee (not a portal) can access if is follower of the task.
Follower rule is not enough as a user creating a rule will subscribe to the rule but to subscribe to record, the user should have access to it in the first place.
To make sure the snake does not bit its tail, fallback to give access on task where the user is reponsible (user_id = user.id).
Fixes #139

Adapted the tests to the new behaviour (removed not relevant and added some on creation)
[FIX] hw_escpos: use logger instead of prints to avoid corrupting the odoo.py command line interface.
[FIX] requirements.txt: add info about optional python requirements used for the point of sale receipt printing
[FIX] server.py traceback on ctrl-c from windows cmd

Define a shim signal.SIGHUP on windows to avoid an ifdef in the threaded server
loop.
[FIX] windows ctrl-c from cmd as a non admin

return False when calling is_running_as_nt_service from a non adminstrator
account.
[FIX] website_sale: don't carry over tx details on SO duplication

opw-617319
[REM] python-stdnum from requirements

It is never used in the code, and causes problems with wheels: related
to pypa/pip#2105

closes #3744
[FIX] web: force company logo refresh per db

The company_logo is cached and was not refreshed when switching between database, still showing the logo of the company of the previous database
Fixes #2738
[FIX] decimal_precision: avoid refreshing float precisions at each cache invalidation

Changing the decimal precision of float fields is a rare
operation, while cache clearing occurs fairly frequently.
Signaling a full registry change when the decimal precision
is changed (instead of a mere cache change) is therefore
a better trade-off, and more semantically correct as well.
This way we avoid the decimal precision refresh for each
invalidation.

Registry invalidation implies cache invalidation.
[FIX] mrp: perform location chaining for kit exploded moves

This rev. 7307227 ensured to not (re-)set the state 'confirmed' to exploded moves with a more advanced state (for instance, 'assigned')
Nevertheless, the location chaining is performed on the move confirmation, through the action_confirm method of the stock.move model. Besides, the resulting moves of the _action_explode method had the state 'confirmed' on creation, the 'confirmed' state wasn't set by the method 'action_confirm', meaning that the moves were confirmed without having the location chaining done. Allowing moves to go through the action_confirm method even if the state was 'confirmed' or further triggered the location chaining.

Preventing already confirmed moves to go through the action_confirm method prevented the location chaining, thus.

We now create the resulting moves with the 'draft' state, and then confirm them through the procurement workflow signal 'button_confirm'. Thus, the resulting moves are confirmed by going through the action_confirm method, writing the confirmed state and triggering the location chaining at the same time. We then write the 'assigned' state if necessary.

opw-617235
[MERGE] forward port of branch 7.0 up to 529e920
[FIX] graph.py: correct Node() creation.

Fixes #3730
[IMP] doc: incorrect value documented

closes #3761
[REM] duplicated package in requirements, sort
[I18N] Update translations from Launchpad 8.0 branches