[FIX] point_of_sale: fixed rounding issue for pos order when discount added(maintenance: 615322).
[FIX] hr,mail: correct remove of suggestions.
[IMP] stock: added missing 'context' parameter (opw 616952)
[FIX] project_timesheet: missing timesheet for tasks without project

Timesheet activities (hr.analytic.timesheet) are generated when a work activity (project.task.work) is logged on a task.
These are updated if the project of the task is modified.
This patch applies the same behaviour for tasks without project, the timesheet activities are generated once a project is set on the task.
To avoid redundency in the code, extract the computation in a distinct method.
Fixes #701, opw 609481
[FIX] mrp: prevent suppression of bom if used in mo

The field bom_id is required on a manufacturing order and deleting a mrp.bom would block the current mo.
Restrict the suppression for manufacturing order in progress.
Fixes #3417
[FIX] project_timesheet: accept work without date

date field on a project.task.work is not required while it is on the hr.analytic.timesheet (with default value).
Avoid error if fill a task work without date, fallback on context_today.
[MERGE] forward port of branch 7.0 up to ab5ecef
Merge pull request #3220 from odoo-dev/7.0-opw-615322-rgo

[FIX] point_of_sale: fixed rounding issue for pos order when discount ad...
[FIX] web: date autocompletion should use user's locale

search bar does not suggest date field format based on user's locale and always shows based on mmddyy using Date.parse,  opw:615276

Note: starting in 9.0, datejs has been replaced by momentjs, so this
problem should be solved in a better way.
[IMP] Speedup test account_assert_test.xml in account
[IMP] Pass the invoice type from sale to picking for the sale_journal module that is installable again
[FIX] layout: add alt on logo for seo
[IMP] purchase: error message linked to product, not company
[FIX] stock: multicompany reception

When a picking is confirmed, the generated account.move(.line) should take the
company, accounts, journals and period with the same company as the picking,
not the one of the current user.

This was problematic if a user in a company confirm a picking linked to
a purchase order done in another company.
For real time valuations, the generated accounting entries were mixing both
companies.

Fixes #3466
[FIX] product: more accurate name_search

First, name_search searches on default_code, then, if the limit is not reached, it searches on the product name
The results found from the default code search must be removed from the search domain when doing the search on the product name, to avoid having results already found by the search on the default_code

opw-618015
[FIX] point_of_sale: missing multi-company rule
[FIX] api: avoid to return all fields *2many in onchanges

When an onchange returns a change in a 2many field line (a '1' tuple, update), avoid to return all fields of the *2many field but only the altered field.

Otherwise, the web client regard all the fields of the 2many as dirty, and try to write on all fields (even if the value is the same, thus)

opw-615062
[IMP] add link to write method in documentation
[FIX] account: allow to use quantity in taxes computated with python code
[FIX] web: do not set the one2many dirty on field validation

This rev. 06104ba553702b16878d52c5b8ab089355216a5e

Added the dirty flag on the o2m field when the editor of the editable list was enabled (meaning that the editable list has been altered)) because the dirty flag was not set correctly by the one2many during the edition, at the time.

It looks like this is now the case

Besides, as now, we valid all the editable list of the form, wether or not the editable list was altered, we must not set the o2m as dirty anymore.