Steph wrote: A snapshot is a separate concept from a configuration. Building a separate tool to create snapshots is a good idea. A snapshot should know about a configuration but not the other way around. The problem we run into is that we use configuration A that depends on version B1 of a configuration, and another configuration C that depends on version B2. So we need to create a new configuration version of A, even though A is not interested in C. To make that work dependent configurations would need to change at the sum of change rate of all the configurations they are depending on. As long as we don't have global flow (in the lean sense) that is unworkable. Yes. Make snapshots. And a good experiment to get tools improved would be to add a ConfigurationOfPharo build that creates a version for each build. I suspect some scalability issues. Stephan