This idea is about DQP deployments, where development is on D system, quality deployment on Q and production on P.
The idea is, that on production environment (env=prod) it should be possible to use long life caches, for just everything. Templates, extensions, content and so on.
BUT, if content/template/extension promotion between environments the git-server-module is used, we need some way to invalidate the caches. So maybe the git module fires an event, that causes all caches to be invalidated.
This idea is about DQP deployments, where development is on D system, quality deployment on Q and production on P.
The idea is, that on production environment (env=prod) it should be possible to use long life caches, for just everything. Templates, extensions, content and so on.
BUT, if content/template/extension promotion between environments the git-server-module is used, we need some way to invalidate the caches. So maybe the git module fires an event, that causes all caches to be invalidated.