[ADD] README.md for CRM
[FIX] website_sale: correct "buy product" tour to search the product before selecting it
[IMP] Maifest for Github README.md on main apps
[FIX] website_sale: partially revert 086cfd5.

Use less specific css selectors in "buy product" tour.
[IMP] ORM: Coalesce NULL boolean values to false when generating ORDER BY

After commit f28be81, boolean columns may have more
NULL entries than before. In the (rare) cases where
a boolean column was used for an ORDER clause
(e.g. in the /shop page of website_sale), this
causes a change of the resulting ordering.

By coalescing NULL values to false in SQL,
we make the ordering consistent with what the
framework does for domain expressions with booleans,
and when reading boolean values, that is, NULL is
the same as False.
[IMP] Footer message according to installed apps
[IMP] Average price correction + Lot should be changeable in bar code interface
[IMP] Gives warning when the product needs tracking in bar code interface + pack ops with packs don't need lot for related moves
[IMP] is_product_variant not needed in most views + no delete in stock valuation history
[IMP] No attrs for taxes and income/expense accounts
[IMP] Condition tag would not be upgraded when migrating
[IMP] Type manufacturing orders, remove double accounting entries, child_of, push rule global has no route
[FIX] Change two-one step wh, multi-comp wh, quantity field float, show product_uom_qty instead of product_qty in mrp production for moves
[FIX] Don't change to product_uom_qty if not move
[IMP] Not necessary as operations are computed, but more logical to do action_pack as dropdown(process)
Merge pull request #1663 from odoo-dev/8.0-wmsstaging5-jco

8.0 wmsstaging5 jco various fixes from support and github issues
[IMP] models.py: _auto_init: accelerate row existance check

Using `COUNT(1)` on big table can be slow. Use `min(id)` which use
pkey index to have a quicker response
Merge remote-tracking branch 'odoo/8.0' into 8.0-stock-partial-picking-back-qdp
domain on source and dest locations
[FIX] orm field (new api): preserve empty values instead of folding to False

The new API introduced a small behavior change where empty
string values written or stored in a char/text field were
replaced by False (i.e. as if they were NULL).
This was done to mimic the web client behavior, but introduces
a very surprising effect: a.name = ""; assert a.name == "";
would fail. It would also require many more tests in the
code when reading existing required values from the database,
as they could still be False when an empty string value
had previously been stored, for some reason.