Insert runtrace debug whenever DevelopmentMode is enabled
Only turn debug on with a diazo.debug flag
Include diazo-debug resources
Preparing release 1.1b1
Back to development: 1.1b2
don't (explicitly) depend upon `plone.app.controlpanel`

it's already required by `Products.CMFPlone` in which we're trying to merge `plone.app.controlpanel`...
Make comment match reality
Route all error_log output through generate_debug_html

This means that even if the theme doesn't even compile, diazo can show
useful debug output.
Need at least 1.0.3 to do debugging
Show errors when theme doesn't compile, regardless of diazo.debug setting
ThemeTransform.transformIterable must return a serialized content so if GZipTransform is part of the chain, it will change it in an iterable safely.
those new gzip tests are actually NOT failling without the related fix in ThemeTransform.transformIterable, but there is not obvious way to reproduce the https://dev.plone.org/ticket/12038 bug with browser test (nor selenium by the way).
fix https://dev.plone.org/ticket/12038
theming/caching integration tests
Add plone.app.caching egg for tests
restore original implementation, the problem is not here, it is in plone.app.caching.operations.ramcache
test_cache_with_GZIP_anonymous does fail now, reproducing the https://dev.plone.org/ticket/12038 bug
update history.txt
Merge pull request #11 from plone/ebrehault_fix_12038

fix for non-themed pages for anonymous + gzip
The id for the base div changed