[FIX] User Partner Company has to same as User Compnay not as usder company
[MERGE] Parent Sync (70)
 - Allow setting the company_id of the partner to False in order to make the partner shared between all companies.
[merge] lp:openobject-server/7.0
[IMP] res.partner must only allow to set the company_id of a partner if it is the same as the company of all users that inherit from this partner
[FIX] fix demo data problem, now able to assign company to existing partner which does not have
any company. Did small variable name change
[IMP] removed unused user pool
[FIX] Skip register reports that have xsl but no xml
[IMP] document create/delete=false in view definitions
Launchpad automatic translations update.
[FIX] ir.filters: deduplicate redundant ACL on ir.filters

By default everybody should be able to read and modify
filters, and this is coupled with a global ir.rule that
only permits viewing and touching global filters and
owned filters.
[IMP] update the documentation patch

add all supported attributes
add list of supported views
add example use case
add information about the default value of these attributes
Launchpad automatic translations update.
[DOC] module dev: description of view attributes @edit|@create|@delete, courtesy of Alexande Fayolle (Camptopcamp)
[FIX] res.partner: current name_search() implementation tends to skip a few valid results during early autocompletion - mitigation attempt

The main reason for the semi-random behavior
observed during auto-completion is the
missing ORDER BY clause in the pre-filtering
SQL query.

The ORDER BY clause is expensive but inevitable
if we want to apply a correct LIMIT, otherwise
we would return random `limit` results among
all the possible matches.

The current SQL query seems convoluted due
to the duplicated CASE clause but it
performs slightly better than the equivalent
CTE-based (WITH...) query, so it was preferred.


There is still a chance of returning too
few results due to double limit application,
as further discussed in bug 1203727
Launchpad automatic translations update.
[MERGE] res.partner: current name_search() implementation tends to skip a few valid results during early autocompletion - mitigation attempt

The main reason for the semi-random behavior
observed during auto-completion is the
missing ORDER BY clause in the pre-filtering
SQL query.

The ORDER BY clause is expensive but inevitable
if we want to apply a correct LIMIT, otherwise
we would return random `limit` results among
all the possible matches.

The current SQL query seems convoluted due
to the duplicated CASE clause but it
performs slightly better than the equivalent
CTE-based (WITH...) query, so it was preferred.


There is still a chance of returning too
few results due to double limit application,
as further discussed in bug 1203727
Launchpad automatic translations update.
Launchpad automatic translations update.
[FIX] modules.loading: extra loop when installing/upgrading modules to help solve missing deps

In some rare cases the dependencies have changed, and modules that depend on an uninstalled module
will not be processed on the first pass.