bzr revid: fva@openerp.com-20131216155723-nnlv8223v9fr70nn

bzr revid: fva@openerp.com-20131216152113-3y2s2fva3wvguoxt

bzr revid: fva@openerp.com-20131216143559-6unghp0sza9ihs4r

bzr revid: fva@openerp.com-20131207170616-je7r27nb6n2wsrq0

bzr revid: fva@openerp.com-20131207170014-9pctopzgx5ahtb21

bzr revid: fva@openerp.com-20131206145635-kjsm7hi2psblxb3t

bzr revid: fva@openerp.com-20131205175325-8v81lfj69020x0qe

[MERGE] [FIX] account_anglo_saxon: at invoice validation, the price for the analytic lines should be computed using the price_unit of the related stock.move instead of the product standard price (useful if different valuation method, could have price difference between delivery and invoice time)

bzr revid: mat@openerp.com-20131205163802-chgmkik9qj0s5kw6

[FIX] account_anglo_saxon: at invoice validation, the price for the analytic lines should be computed using the price_unit of the related stock.move instead of the product standard price (useful if different valuation method, could have price difference between delivery and invoice time)

bzr revid: mat@openerp.com-20131205163406-3rvupbbj3sm9q550

Including:
- sales team members are displayed
- fixed sparklines whose numbers were incorrect
- sparklines now redirect to a correct report view, filtered for the sales team, grouped by month, in order to have matching results between the vignette links and the displayed reports
- custom css in crm put in a sass file
- sale_crm extend the crm reports, to add the section_id field in the reports, allowing to filter / group by salesteam. The analysis view has been put into several methods to allow extension.

bzr revid: tde@openerp.com-20131205160029-1tljp52ovcavwxel

[IMP] web_kanban_sparkline: added an option to add a suffix in the sparkline tooltips

bzr revid: tde@openerp.com-20131205160010-8ecv8b618fa6rywj

bzr revid: tde@openerp.com-20131205151424-kctwivphai3kspkz

bzr revid: tde@openerp.com-20131205151355-p2vtq5s1etv145my

bzr revid: tde@openerp.com-20131205150337-5lwc6w7whrtlwp5d

bzr revid: tde@openerp.com-20131205145344-y7ierj85glu439l7

- sales report: the group by salesteam was wrongly placed in the view
- sale_crm: fixed computation for sparklines, now bar graph should display the same
result as the sales analysis
- added a forgottent cursor: pointer for a gauge
- moved the gauges in the dom
- sale_crm: report: removed extra content not necessary

bzr revid: tde@openerp.com-20131205144505-jfsd8lh91r1b13a1

[FIX] crm: sales team kanban view: added an oe_clear beceause of alignment issues when adding things below item_list.

bzr revid: tde@openerp.com-20131205144344-d8616y18n2lvnkgu

- moved css into sass file to standardize the process
- commented some records added in the xml file of crm.case.section that do not seem necessary

bzr revid: tde@openerp.com-20131205124749-3a1quhetgxq2d224

bzr revid: tde@openerp.com-20131205102402-v6p1c1duimd9m59l

bzr revid: tde@openerp.com-20131205102352-ncx6whb8r0fejgcc

When processing an incoming email, we try to find a parent for the email based on references. Before this merge, it was done using openerp-<model-<res_id> pattern. However it is buggy. Indeed having two OpenERP sending emails to each other leads to messages being inserted in a wrong thread (model and res_id of the first OpenERP for both instances).

Now we search for an exact match between the references and the stored message_ids. As each message_id can be considered as unique the number of collisions is lessened. This won't cause any issues with OpenERP >= 7.0.

A compatibility mode is implemented for <= 6.1: as in those versions the message_id is not stored, we fall back on the previous behavior for records having messages without message_id. This indicates that the record was created before 7.0.

Tests have been updated accordingly, and a test added for the compatibility mode.

bzr revid: tde@openerp.com-20131205100534-2rlyun8wqng3qa6f

- removed a debug print statement
- now searching all references once instead of each reference one at a time
to lessen the number of queries; as the newest message will be the first
in the search result, it's ok.

bzr revid: tde@openerp.com-20131205093921-h7sits57vqc51c8p

bzr revid: tde@openerp.com-20131205093609-3lj3hsxz2vsudhw3

[WIP] point_of_sale: more perf improvement, this time on the receipt and payment screen + lots of usability improvements and cleanups

bzr revid: fva@openerp.com-20131204172122-mzl4wg4uw51uzdfv

[MERGE] forward port of branch saas-2 up to revid 9029 chs@openerp.com-20131204125051-dexejzwigpu0z1yy

bzr revid: chs@openerp.com-20131204130023-lgravuoxwlt39pek

[MERGE] Forward-port of latest 7.0 bugfixes, up to rev. 9674 rev-id: dle@openerp.com-20131204133633-t7wfbnipv3jtss82

bzr revid: chs@openerp.com-20131204125051-dexejzwigpu0z1yy
bzr revid: dle@openerp.com-20131204134400-50y7ojeb8pw7k56s

Because defaults get function of partner_id of wizard read the partner_id of the opp and return the first item of the tuple, but if there isnt a partner on the opp, the read return a false for this field, not a tuple. 
No return the first item of the tuple if the partner_id is set, else False

bzr revid: dle@openerp.com-20131204133633-t7wfbnipv3jtss82

bzr revid: chs@openerp.com-20131204122609-oi2b8g4p8cy13dux

bzr revid: chs@openerp.com-20131204112734-2h569udrxgsgw9kr

In im_session model, field channel_id was a many2one to im_user, or, obviously, this should be a many2one to im_livechat.channel
Well, obviously, this is a copy/paste error (or distraction, your choice!). This fix should normally not be pushed on a stable branch (like the current one, saas-2), but considering the severity of the problem, and the few changes in database (alter foreign key only), this is acceptable. Why such a big mistake has not been seen earlier ? Do you even test or read back what you write ?

bzr revid: dle@openerp.com-20131204122727-q0ch5j2v8rrli41e

bzr revid: chs@openerp.com-20131204102430-qxqk8qtze5n5rqe8

bzr revid: launchpad_translations_on_behalf_of_openerp-20131201054445-5fy8zd7lvnn9mjp2
bzr revid: launchpad_translations_on_behalf_of_openerp-20131202055138-hq05otjnuktjpa48
bzr revid: launchpad_translations_on_behalf_of_openerp-20131204055601-tbzqqhperzffjbjt
bzr revid: launchpad_translations_on_behalf_of_openerp-20131204055642-0rwynvhgvs0r14b3

bzr revid: al@openerp.com-20131203215640-ev45het902u6afls

bzr revid: al@openerp.com-20131203214705-6tz63yqo9kk73ztx

bzr revid: al@openerp.com-20131203191621-xu2350cw0u3izn3s

- context manager request object (removes some ugly hacks)
- improve http error handling
- add lazyresponses

bzr revid: al@openerp.com-20131203190639-e8r1qm9wc82t8g4k

[FIX]portal_sale: add the lang to the email templates (sale.order and account.invoice), for the email to be translated in the customer language (as this is the case for regular email templates from sale and account modules-

bzr revid: dle@openerp.com-20131203142554-5yrp5o5wl382oyo3

openerpframework.js can be used as standalone library (im_livechat uses
it this way) and do not depend on underscore.string.js

bzr revid: chs@openerp.com-20131203132937-ss7hx1gligzai5ch

[FIX]sale_stock: do not raise if not able to find any warehouse (for the get default warehouse), it can prevent the user of doing anything (if he does an upgrade of sale_stock module while having no warehouse set, the user will not be able to sign in in his instance again).

bzr revid: dle@openerp.com-20131203095544-i5vmow007dgjbiza

bzr revid: launchpad_translations_on_behalf_of_openerp-20131130053134-6u83vcd1133xs8yf
bzr revid: launchpad_translations_on_behalf_of_openerp-20131201054550-w0k8alfqs2bigurx
bzr revid: launchpad_translations_on_behalf_of_openerp-20131202055222-2u7o99e48254dceu
bzr revid: launchpad_translations_on_behalf_of_openerp-20131203061621-hyqqh11jt7g0ilqh