Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module. Invoicing is now managed through
Sale.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- New start and expiration dates
- Remove field Contract Status
- Simplified because use of sale_timesheet

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

New module to centralize UoS management.

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- Partial migration to new api

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- No use of Journal Name

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module. Invoicing is now managed through
Sale.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- No journal since invoicing is managed in Sale
- No invoicing from timesheet

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- No invoice policy anymore

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module. Analytic has been simplified.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module. Invoicing is now managed
completely from the Sale module.

Responsible: fp, dbo, nim

Major changes:
- Remove reports
- Simplify models

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- No analytic account journal on account journal

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Major changes:
- No use of UoS anymore
- No analytic journal (journal_id) on account move lines

Reason: complete rewrite of the Sale module.

Responsible: fp, dbo, nim

Reason: complete rewrite of the Sale module. Invoicing is now managed
completely from the Sale module.

Reason: complete rewrite of the Sale module

Fixes a bug introduced in 5a8a0d25.
Before this, creating an order with two of the same products would
result in a total price to pay which would only include the tax of one
product. This would cause point of sale orders in the backend which
weren't fully paid.

- hr, project, sales_team: no subscribe on create

For header records like sales steam, project, jobs and department, do not
subscribe the creator. Indeed those objects allow to automatically follow
child records (opportunities, tasks, issues, applicants). However those
records are often created by IT / technical / administrators that should
not be followers of all child records. Therefore the no subscribe key
is added in context.

- crm: new lead subtype

The 'new' stage is based on the sequence only, not the probability. Indeed
a new lead does not have a probability of 0; otherwise it is already lost.

- mail_message: fixed internal subtypes

Indeed has_group works only for uid and does not care for any given recordset.
Probably we need a is_in_group method on res.users. Someone smart could code it.

- mail_message: update message before notify

This way in the various notify methods, the message is correclty updated with
needaction and recipients. Also cleaned some comments.

- mail_message: avoid email loops

Do not notify people having the same email as the message / email to propagate.

- mail_message: fix access right issues

When computing recipients and partners to email, use a sudo for some internal
computation to avoid access rights issues. Indeed public user may go through
this method (forum for example).

Employees (base.group_user) can read tasks. However they miss the right to read
task stages (project.task.type). This causes issues when reading the form view
of a task. This commit fixes this issue.

In sales_team, we had 2 fields for invoicing : invoiced_target and invoiced_forecast.
As forecast is useless because someone has to set it manually, we did something different.
The field invoiced_forecast is now invoiced and is computed according to the invoices
associated to the sales team. We can now only set the target.

To benefit from recent changes to minimise the number of exported terms

Makes no sense as it's technical information

Add new website_form module
Spoiler on salepocalypse merge...

A tax is not translatable in standard. The translation of tax name is added in
l10n_multilang module but should not be present in base account.

defining directly 'width: 100%' didn't override the o-flex rule defined outside
the media query.

related to https://github.com/odoo-dev/enterprise-9/commit/9d1327be4940a47769237746bd83a38787fca8ae