Problem
---
We recently had our first Grok release (0.10). Due to various versions
of certain packages, we had to pin down the versions of those packages
to ensure you'd get the version we had tested the release with, and to
prevent buildout from downloading the versions of packages that
Previously Philipp von Weitershausen wrote:
Proposal
I think zc.buildout's version mechanism in buildout.cfg is a good
technical basis. It's simple, light-weight and easy to version-control.
For example, the Grok project could create a grok-0.11.cfg defining the
known working
