[FIX]product: add store=dict to field name_template

bzr revid: csn@openerp.com-20130412130856-3g5e67v2r7y6ep5v
[REF]product: remove one extra loop

bzr revid: csn@openerp.com-20130415102121-u74t7zd3zct3q3ts
[IMP] only recompute name_template if product_tmpl_id changes
PEP8
[MERGE] sale_order_dates: several improvements to usability and planned date computing, courtesy of Lionel Sausin (Numerigraphe)

bzr revid: odo@openerp.com-20140306202430-aw45sqw6og8ezcni
[FIX] sale_order_dates: fixes + deduplication of _get_planned_date()/_order_line_move_date() methods on sale.order

bzr revid: odo@openerp.com-20140306225009-f0jk43x5qpovurxi
[IMP] Add search filters in inventory analysis

Add search filters for products available, out of stock, and with negative stock in inventory analysis
improve looping efficiency
[IMP]: requested_date+commitment_date on quotation
[FIX] product: creation of reference uom

Set a default value for factor when creating a new uom.
Could not create a new UoM with type reference (if creates a reference uom, no need to pass a factor).

Change the readonly filter to (type = bigger) to make the field writable for reference uom.
This is needed to force the reset of the factor when switching of type (onchange_type).
As the field was readonly, kept the old value for factor.
Merge remote-tracking branch 'odoo/7.0' into 7.0
[FIX] project_timesheet: date of created analytic line not in user tz

When the user was in timezone UTC + 1, and added a project.task.work which created an analytic entry line (timsheet activity), if the datetime was set to 11/25 00:00:00, the date on the analytic line was set to 11/24, because this was the truncated stored value(UTC Time), which was 11/24 23:00:00
[FIX] account: prevent invoice line duplication on partner duplication

If a company contact (a partner with a company set as parent) had invoices, and the company of this contact was duplicated, all the invoices lines were duplicated,  on the original invoice moreover (new lines were added on existing invoices)
Merge remote-tracking branch 'odoo/7.0' into 7.0
[FIX] marketing_campaign: typo in manifest
[FIX] l10n_br: remove reference to old base.group_extended group

Fixes #3879
[FIX] mrp: prevent recursion from phantom boms with no lines

if the bom is phantom and has no line, we attempt to find a new bom with the default product uom
This is possible that we find the same bom that the current one
In such a case, we must not explode, to avoid recursion.
[FIX] correctly update many2many in listview (web client)

Fixes the issue #1216 (follow the link for more information). The issue
was caused by a hack in list view: the magical suffix __display is used
in render_cell to determine if a many2many field should be updated. This
commit simply makes sure that old many2many fields + __display keys are
cleared.

A better way would be to redesign/refactor the list view to avoid that
hack in the first place.  But this would be a much more complex task.
Merge remote-tracking branch 'odoo/7.0' into 7.0

Conflicts:
	addons/l10n_br/account_view.xml
	addons/mrp/mrp.py

See https://github.com/OCA/OCB/wiki/7.0-2014-11-27
[FIX] stock: prevent serial number deletion on stock.move

prodlot_id field may be required due to constraint `_check_tracking`.
When a stock.production.lot is deleted, the constraint on linked stock.move is
not checked. To avoid inconsistency, restrict the suppression.
To allow the modification of existing stock.move, remove the states attribute on
the field definition.

As removal of serial may impact the traceability, it makes sense on buisness
point of view to force the modification of previous stock.move, even if the
constraint would not have been violated.
The list of linked stock.move is present on the serial form view making
the operation easier.

Fixes #3560, lp:1176912