bzr revid: fme@openerp.com-20140505160953-yk6688ey7eoz5579

bzr revid: fme@openerp.com-20140505145816-jz7e4byh1imrkaek

bzr revid: fme@openerp.com-20140505131012-owp0qucjbnesp4ee

bzr revid: fme@openerp.com-20140505121036-044ecvq8s3d669b2

bzr revid: fme@openerp.com-20140505113800-wv5vh802us270oez

bzr revid: rco@openerp.com-20140505085739-z2asr1vrx6yyjtlh

bzr revid: fp@tinyerp.com-20140504113847-4xmjg30m5leaqz2c

Many small tweaks/css changes to correctly display the stat buttons in
various situations (with/without icons, with/without strings, with sub 
widgets, ...)

bzr revid: ged@openerp.com-20140502145211-ehnb1v66szw7nl01

This branch converts pretty much every buttons in 'stat buttons',
which means buttons that can display any kind of information.  Right
now, it is mostly used to display a numerical information (such as a 
number, for example 9 Calls).  Also, look at the invoices button in 
Customers form view for an example of a functional field, displaying
the total amount invoiced.

The stat buttons also supports sub widgets, for example a mini pie chart
or a mini bar chart.  Examples of such sub widgets can be found in 
marketing/mass mailings form views (not ready yet)

bzr revid: ged@openerp.com-20140502144544-c5j7bzlm9i4clv4l

bzr revid: ged@openerp.com-20140502132258-88x9mam35o3k5ndm

bzr revid: ged@openerp.com-20140502130753-4z24z1to9pkrckvq

bzr revid: ged@openerp.com-20140502123355-9dqpwq1g9rrpisxj

bzr revid: al@openerp.com-20140501212023-x9r57i05nrr0g29f

bzr revid: fme@openerp.com-20140501210507-cbl9no3o92zkdq5h

bzr revid: fme@openerp.com-20140501210436-osyrvlue41w63i6f

bzr revid: al@openerp.com-20140501205153-ko00g1vyyrmc21k8

bzr revid: al@openerp.com-20140501204242-jngte754yqyj4nb0

bzr revid: al@openerp.com-20140501200150-5u3lfdqls3t3oeih

bzr revid: al@openerp.com-20140501191831-mhsrpgza1x00ysy4

bzr revid: al@openerp.com-20140501190544-egvc85ctdxs69cmr

bzr revid: al@openerp.com-20140501184217-pgi1gzbdpysdybog

bzr revid: al@openerp.com-20140501172508-tjennzht30ktw3nz

fix fp commit to use debian compatible werkzeug api data instead of set_data

bzr revid: al@openerp.com-20140501165004-0e6xp8e9hdpifofj

bzr revid: fp@tinyerp.com-20140501161452-0pw17e2v0cjjlupm

bzr revid: al@openerp.com-20140501152604-4cobh5ui47dt4pem
bzr revid: al@openerp.com-20140501155633-gefnc3zqcsr2rhaz
bzr revid: al@openerp.com-20140501161156-4wbsvhh8gz4r22h3

bzr revid: al@openerp.com-20140501161108-50yidx30rm6z7d10

A deadlock occurs when
- phantomjs_test1 is executedd, enter_test_mode is activated
- console.log('ok') is issued, sigterm is sent to phantomjs_test1 process
- phantomjs_test1 is finished and leave_test_mode restores the registrymanager lock
- phantomjs_test1 process, just before dying, makes a last http request phantomjs_test1_last_request
- phantomjs_test1_last_request thread will wait for the registrymanager lock, when all tests will be completed 
- phantomjs_test2 is run, enter_test_mode is activated
- phantomjs_test2 is reach its end and _wait_remaining_requests is called
- phantomjs_test2 _wait_remaining_requests hangs forever waiting for phantomjs_test1_last_request

bzr revid: al@openerp.com-20140501150641-ua0b7pntesgm3n5p

[MERGE] Forward-port of latest saas-3 bugfixes, up to rev. 4007 revid:dle@openerp.com-20140501121633-6umc2sxwi0h0lhay

bzr revid: dle@openerp.com-20140430123818-zzdxmat4c5yg9gg7
bzr revid: dle@openerp.com-20140501121915-q88k37nd25ietw8c

[REVERT] 2 previous revision, as it looks like that the fix causes more troubles than it resolve a problem

bzr revid: dle@openerp.com-20140501121633-6umc2sxwi0h0lhay

bzr revid: fp@tinyerp.com-20140501114003-5xs31o0lzpp8ru2s

bzr revid: fme@openerp.com-20140430151509-mme5st89o1hj4zcs

bzr revid: fme@openerp.com-20140430151302-e42monb4klz4udw5

bzr revid: fme@openerp.com-20140430151137-c4ue5ko0vdyvoijt

bzr revid: fme@openerp.com-20140430142025-nbvwk5ggzo1bro0q

bzr revid: ged@openerp.com-20140430140625-83w6v1oql62r5jly

bzr revid: ged@openerp.com-20140430085942-umusyhp4cs2ffezj
bzr revid: ged@openerp.com-20140430140423-kq0vdboq1mux4zfn

[IMP] purchase: invoice creation more modular/extensible through the introduction of a _prepare_invoice method()

This is similar to what was previously done for Sales Orders.

bzr revid: odo@openerp.com-20140430140103-hfumie3ndvlodgeh

bzr revid: fme@openerp.com-20140430132636-p42ehcb0dnc1d3jx

bzr revid: fme@openerp.com-20140430132510-smhi39h9oyi8p4nt

bzr revid: dle@openerp.com-20140430131739-ywyqb1gh68xbxid1