* Odoo installation from packages or source
* Deployment instructions for production environments
* dbfilter

Add missing support for disabling xmlrpc(/http), useful for WSGI
deployments which require running cron-only Odoo instances.

This simple optimization in load_marked_modules() avoids unnecessary calls to
load_module_graph().  This provides a small speedup, and avoids confusing log:
some module updates were making it look like the registry was loaded 5 times
instead of once.

[FIX] website_instantclick: this lib create some bug because the odoo assets are loaded in the body and some event are binded more of one time. Change the js lib  because the xml can't be change in 8.0. TODO: move assets into the head and fix js files and remove this commit in master

only create db

Revert "[IMP] calendar: Set default value for start* and stop* date/datetime. Else field.function start and stop are not setted by default while they are required."

This reverts commit b1adf3a9.

Not so simple, 'search' don't find recurrent events with this change

This is related to rev. db98434e

rev. abe5c803 forgot some partial reconciliations when the date domain was other than BETWEEN (for instance, <= stop date or >= start date, alone, not between)
Besides, the rev. abe5c803 did not care about account move being posted or not.

rev. db98434e took several times the same partially reconciled moves lines

[IMP] calendar: Set default value for start* and stop* date/datetime. Else field.function start and stop are not setted by default while they are required.

session.get_file appends the json to the body of the generated iframe and
then tries to json.parse it by reading contentNode on the body.
Exceptions from `report_download` method may contain `<` and `>`, so when
json.parse tries to json.parse the contentNode, it reads only a part of
the original json string. htmlescaping the json string solves the issue
by preventing the content of the json string to be interpreted as html.

Another fix should probably be build for purchase price, but it isn't that easy, we need to know the partner to which the product has been purchased, as taxes are partner/country dependent.

Besides, included taxes in purchase prices happen less often.

Fixes #4196

Just a little bit.

closes #4205

Default Currency for Malaysia is MYR (Malaysian ringgit), not MXN (Mexican peso)
Fixes #4193

Tree view gives no information
Fixes #4195

[IMP] Changing product qty on product form should work with serial numbers like in 7.0, but we should explain it
Closes #3984

[IMP/FIX] account: bank statement reconciliation widget: adopt a more logical approach to reconciliation balancing, as explained in https://github.com/odoo/odoo/issues/4017#issuecomment-66599534
Fixes #4017

In the new api an empty recordset converted to string is the name its class
while previously it was converted to an empty string.

The valid v7 condition sould have probably been
    move.picking_id and move.picking_id.name or False
but in v8, simply move.picking_id.name is enough and avoids getting these
accounting entries strangly named when there is no picking.

If a wizard is launched from an embedded view list, only the record of the line from which the wizard was launched is reloaded after closing the wizard.

In this specific case, as new lines are added to the picking, we need to fully reload the stock picking

[FIX] point_of_sale: the search in product or partners could crash if there were a number followed by a colon

Shipping and invoice addresses header are now bold and sticked to the related
address.

on_change_user was used to assign the first team  in which the user is a member to the lead
When the user does not use the multi sales team, it therefore set a default sales team, but invisible to the user.

Stages displayed in the kanban view are the lead sales team stages. In a non sales team env, only stages with no stages are displayed for new leads
If you added a new stage, in the kanban view, the stage is not assigned to a team

closes #4169
closes #4170

In some cases when the move was partially reconciled, the amount of the move wasn't added to the total
This is related to rev. abe5c803

closes #4166

Non-setup fields could cause problems in two places:
- when traversing the chain of fields in related fields;
- when adding recomputation triggers on inverse fields

Both issues are fixed by this patch.