point_of_sale: Add _prepare_analytic_account method to easily set analytic account from custom module
[IMP] .gitignore maintenance migration scripts
[FIX] base_action_rule: Make sure model exists before trying to wrap hooks

In certain cases, before running an update unregistered models will try to
register hooks. Trying to wrap create and write on these will cause
AttributeError on model_obj which would be None

Signed-off-by: Sandy Carter <sandy.carter@savoirfairelinux.com>
[FIX] core: correct cron thread registry iteration

Fixes #3387
[FIX] website_sale: don't display twice some products

In list view, the 10 last products of a page were the 10 first products of the next page.
Fixes #3373
[FIX] report: fix report HTML editor scrollbar in Firefox
[FIX] purchase: fixed product_uom and price_unit update on product_id change on purchase.order_line form view
[FIX] fields: make field.store=False on old-style function fields

Clarify the semantics of field attributes:
 - field.store is True when the field is actually stored in the database;
 - field.column is the column corresponding to field or None.

The various field definitions correspond to:
 - new-style stored field: field.store and field.column
 - new-style non-stored field: not field.store and not field.column
 - old-style regular field: field.store and field.column
 - old-style function field: not field.store and field.column
[FIX] account: domain on wrong field

The store recomputation method failed as the search was made comparing id of account.move.line to the account.journal values. Search was returing no result most of the time (opw 615554)
Fixes #2454
[FIX] packaging: debian: set /var/lib/odoo as odoo user home dir
[FIX] project_issue: explicit store attribute for the progress function field

This is a workaround for an ORM limitation. A stored function field is
not updated when it should if the "source" field is also a stored function
field
[REM] project_timesheet: report_timesheet_task_user
[FIX] account: default partner format

When creating a new account.move.line, the computation of the default values should accept both `id` and `(id, name)` format.
The key partner_id may be containing a tuple so browsing should only be done on the first element of the tuple.
Fixes #3386
[IMP] doc: link logo to current doc's root, not to odoo.com
[IMP] doc: add link to company website in footer, fix release version
[IMP] doc: link directly to edition mode in docfiles
[FIX] updates the graph view documentation

It was wrong.
[FIX] fix bouncing buttons (when no content)

i am aware that this is an interesting hack, and that i do not resize
correctly the $buttons after the bouncing effect, but at least, it
solves the problem.
[IMP] stock: avoid errors with picking without quantity

When a line is not present in the partial delivery wizard, computation variables are initialized with generic values (zero quantity, zero price,...). Instead of setting the uom to False, keep the quantity of the move.
This makes a difference only when the quantity of the move is 0. That means that the move will be marked as complete and can be processed.
This avoids trying to update the stock.move with a uom at False. opw 616844
[IMP] add a 'or' operator between custom filters (web)