[ADD] add new test for onchange on one2many field
[IMP] mail,website: improve update_notification
[FIX] models: improve implementation of _compute_display_name()

The method was expecting that name_get() returns complete and in-order values.
Because of this, some records in the recordset could end up without a value.
[FIX] display problem in graph view in some cases

Recently, the graph view was changed to prevent changing groupbys
for active custom filters.  Unfortunately, I did not take into account
the fact that pivot table can be drawn in part when expanding rows.

The "frozen" parameter was then undefined and caused display problems,
this patch should fix the issue.
Merge branch 'acsone-8.0-onchange-one2many-test': add test for onchange on one2many field
[FIX] website_hr_recruitement: Don't use GeoIp if all countries is selected
[FIX] web: traceback in search view when no field
[FIX] packaging: windows: passlib dependency was not correctly set
[FIX] fields: convert_to_read, handle missing many2one foreign keys
[FIX] account: account_invoice's onchange_partner_id uses the first partner bank account if several are defined. Merge of #2280
[FIX] request.website browse record bad context
Update README.md
[REM] report: remove openerp/report/pyPdf

Distributing our version of pyPdf is not required anymore since we
introduced the new reporting tool.

In order to keep reports working, the standard python library
`python-pypdf` has to be installed instead (through pip or your
distribution's package manager)
[FIX] models: make field inheritance work when source field is defined in old api
[IMP] sale: quotation confirmed mail subtype defaults to True
[FIX] share/wizard: fix new-api method call incorrectly passing context
[FIX] ir.translation: translated terms within view definitions were not loaded

The changes for QWeb template translation have introduced
res_id values in PO comments for all `#: view:` terms, as
the real database id needs to be resolved when loading them.

For non-QWeb views this is not necessary and actually caused
the terms to be dropped when the res_id could not be resolved.

Rather than having a different PO comment format for QWeb and
non-QWeb views, we can extend the QWeb hack to force the
res_id to 0 for non-QWeb views.

Fixes issue #1755
[FIX] ir.ui.view: match translated terms without heading/trailing whitespace

As the whitespace is stripped when exporting terms
to translate, it must be done as well when matching
translations at runtime.

Fixes issue #1755 partly
[FIX] web_calendar: make UI string translatable

Fixes issue #1755 partially, when the new term
will be translated
[FIX] account: invoice view - useless trailing spaces in labels