[FIX] apply gevent code since 7.saas~3 + decode 7.saas~X release as (7, X) release instead of (7, 5)
launchpad #1244721: fixed final reporting of upgrade script with python 2.6
buildbot: added pyPdf dep, that's not listed in setup.py (report module)
Providing environments initialization in runtime.session

This needs further testing, in particular with older OpenERP/Odoo versions
Besides, the current Odoo master version that this has been developped
against calls itself 9.0.0 alpha, one needs to check if the problem
exists for the 8.0 branch.

At this point, I'm not really sure of what happens for a script that would
spawn several threads.
gevent script generation backported to version 7.saas~3 and following
Merged support new Odoo API related environments init
Fixed minor pep8 warning
Removed now useless test teardown debug print
launchpad #1208745: don't fail if [paths] if missing in .hg/hgrc
[hg] missing unit test for archive()
Minor pep8 warning
[hg] proper UserError in offline mode if repo dir is missing
launchpad #1208745: unit test for the case where .hg/hgrc is missing
[doc] clarifications about db_version and commits in upgrade scripts
launchpad #1343518: fixing shadowing issues with Git layout
launchpad #1343518: previous commit precautions where tautological

Indeed, it added 'addons' to sys.path only if it does not exist.
And we know that at least on recent 7.0, it's a big problem that it actually
contains addons.

In other words, I was over cautious, we have to bite the bullet.
Keeping the ``is_git_layout`` boolean, though, it may prove useful for other
reasons.
launchpad #1249011: made it clearer that a buildout.cfg is needed to bootstrap
dev version was wrong
Fix test that depends on recipe's setup.cfg

Obviously, it'd be better not to be affected by the recipe's setup.cfg at all,
but at leasti this way, the test does not give a false positive during the 
release of the recipe
Release 1.8.5