* event, website_event, website_forum,
* website_hr_recruitment, website_sale

Website access rights were buggy. The editor assets and website editor
assets have to be loaded together to work so the previous behavior
which only loaded one with the restricted access right was not right.
Also, people which had the "Manager" access right for model like event
or job only got access to creation and edition of those objects if they
had the full access to website access rights.

Now the website module creates the two same groups :
* group_website_publisher: load all editor assets, give access to
page creation for model the user has access (event, job, ...) and
edition of those pages
* group_website_designer: implies the first one and give access in
creation and edition of all pages + access of all website menus

The manager access rights for event, product, jobs, etc now implies
the group_website_publisher group for the user (so that the manager
have the editor assets and editor ui).
Note: some python codes use the group_website_publisher for no right
reason, this has to be adapted.

For historical reasons, `vobject`* Python library is not mandatory in
Odoo.

Since refactoring 6af6148a,
get_ics_file() returns now a dictionary whose keys are calendar.event
ids and values are the corresponding ics file.
If `vobject` is not available, it returns an empty dictionary that
could cause calendar.py to crash because it always expects to find the
event's key.

Before this refactoring, this method was called and architectured in a
different manner, so no crash was happening.

This commit prevents the crash if `vobject` is not installed and logs a
warning.

*vobject allows to generate iCalendar files

There was no bug but now the behaviors are more consistent :

- Demo data now declare a black invisible filter instead of nothing.
This allows user to see the effect of filter intensity option
(otherwise it had no visible effect since there was no filter color).

- If the filter intensity is set to "None" (invisible filter) and that
a filter color option is highlighted or chosen, a "Low" filter
intensity is automatically highlighted or chosen so that the user see
the filter color he is chosing (instead of having to choose the filter
intensity first).

- Hide the "Size" option on the blog list page since it has not visible
effect there.

- Some code "performance" improvements in option selection.

[IMP] mrp: create graph and pivot of duration_expected of workorders related to a workcenter and add stat button with load to come

This replaces the old workcenter load report

[REM] mrp: Remove unnecessary stock_move_consume wizard and stock value variation and workcenter load report

`display_start` was wrongly change to `Date` type during convertion to
new-api.

rounding field of product_uom now has sql constraint > 0. If set at 0 it rounds
any quantity to 0, which is never a desired result.

Allowing 0 made it so that some users that did not understand the rounding, set
it to 0 and complained that their quantities were messed up.

Also added translations to the error message.

This improvement adds two default filters and group bys to the supplier
pricelist search view: filters(active,archived) groupby:(product,vendor).

This fix renames filters in purchase from Invoiced (resp. Not Invoiced)
to Received Bills (resp. Waiting Bills) to be consistent with the states
of the Purchase Orders (i.e. 'Waiting Bills'). The erroneous tooltip of
the Bills Received was also corrected.

In procurement form view display a Purchases stat button that redirects to
the purchase order. It opens the PO form view. Note that Purchase Order field
in Extra Information is left untouched. It is just a shortcut to ease
usability.

As this button redirects to the Vendor Bills page, let us rename this
button so that names match.

It is already defined as a payment method (subtype=inbound) and that's what we want. No need of adding 'electronic' in 'payment_type' selection (that crashes if we select that, btw) and 'payment_method_id_code' is a duplicate of 'payment_method_code'.

It should redirect to the web.base.url of the
instance, and not www.odoo.com

'Project > Reports' menu show 'Tasks Analysis'. But
if you install project_issue, or rating_project, some
children menus are added, making 'Tasks Analysis'
invisible.

Trying here to set the same order for issues, ratings,
forecast as in other menus, labels and kanban card.

Set date_assign if a user is assigned to task
even if it is created from the wonderfull quick
create on kanban view.

That bug was introduced when removing the invoice workflow, where a call to action_invoice_cancel() has been used instead of action_invoice_reopen() which does slightly different things, as you can imagine.

Add a space in auto-computed description of account_invoice_line when a product with a code is chosen.

This fix prevents from giving the reason of the refund to the draft invoice created if you select the 'modify' option when refunding an invoice, which now keeps the description of the original invoice.

This fix corrects the inconsistency of the 'discard' and 'cancel' buttons of the tax adjuments wizard

This fix allows users to view the form of the invoices they accessed through the payments (via the 'invoices' button)

This fix allows user to duplicate bank accounts in the accounting module

The field (commented) was removed during migration

Commit 3c98c78f added the feature to be proposed redirection
after a click on a menu link in edit mode. This however applied to main
direct link in the menu and not sub-ones in sub-dropdowns. This commit
fixes this.

As the <strong/> tag which surrounds the "Use this tag" sentence also
contained a <a/> whose href is a computed one (t-att-href), the strong
was not able to be edited.

It was used to correct source in stable without breaking the translations.
In master it should be corrected with real translation

Because 0% taxes will appear in the account.invoice.tax object of the invoice and the account, if null, will be the expense one which is confusing.
Because 44000 is use as everyone as payable account, so removed duplicated 'Fournisseur' account

This reverts commit 20e19fdf.

Already fixed by @fwi-odoo in 82b83ac7

Adding the attributes leave all the old variants available.

While not completely intuitive, this behaviour is not inherently
wrong. However, on the first attribute addition, it leaves a variant
with 0 attributes that can cause problems in the ecommerce. This commit
make it so that this empty variant is archived.

This allows people to create modules under the 'Odoo Proprietary
License' version 1.0 rather than having to rely on the rather vague
'Other Priorietary' license.

The text of the license can be found at:
https://www.odoo.com/loempia/static/examples/LICENSE

This should already have been in Odoo 9 but was mistakenly left out.